Created attachment 178542 [details] Firebird embedded test database In the table designer, when you create a date field and assign it a default value, the assigned value is modified depending on the actions you do in the designer. For example, if you select another field and return again to the date field, the value assigned by default has been modified, it is also modified if you save the table but do not close the table designer and also when you close the designer. In addition, the value that is inserted in the table when adding a record is *completely different* from the value that remained in the designer when it was closed. Steps to reproduce: 1. Create or open a database 2. Create a new table 3. In the new table, create a field called ID, type INTEGER and AutoValue (primary key). 4. Create a new field called e.g. Fecha of type DATE and set a default date, for example 01/01/2022. Change the format fiel to date DD/MM/AAAA 5. Select the ID field 6. Select the Date field again, the default date will have changed to 03/01/2021 (or another value different from the original one). 7. Click on the Save icon, the date in the default value field will change again with each click. 8. Save the table and assign a name to it, close the designer and open the table to enter data. 9. Insert a record to see the date that is assigned by default, it will be a completely different date from the one assigned by default in the table designer (in my case, the last value in the designer was 09/01/2021 and the date assigned by default was 02/01/0009). Expected: 1. That the default date value is not modified whatever action is done in the table designer. 2. That once the table is designed, when inserting records, the default value assigned when designing the table is automatically entered in the date field. Tested with: - Firebird embedded - HSQLDB embedded - MariaDB 10.6 Direct connection on :Version: 7.3.0.3 (x64) / LibreOffice Community Build ID: 0f246aa12d0eee4a0f7adcefbf7c878fc2238db3 CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL And tested with: -HSQLDB emnbedded on: Version: 7.1.7.2 / LibreOffice Community Build ID: 10(Build:2) CPU threads: 2; OS: Linux 5.11; UI render: default; VCL: kf5 Locale: es-ES (es_ES.UTF-8); UI: es-ES Ubuntu package version: 1:7.1.7-0ubuntu0.21.04.1 Calc: threaded
Parts of this are a duplicate of Bug 102945. Jumping to days in the future every time when switching from date field in table design to another field is reported. Please don't mix different buggy behavior in one bug. I changed this bug to the totally wrong value, which is shown in the table when input new values. You could get the "right" values if you change the format of the date in table design to YYYY-MM-DD. See https://bugs.documentfoundation.org/show_bug.cgi?id=102945#c0 Then you have to switch back the format when table is saved and you will try to input new data. The buggy behavior with total different default values when editing a table and opening the table for input data in other formats than YYYY-MM-DD I could confirm with LO 7.3.1.1 on OpenSUSE 15.3 64bit rpm Linux.
Dear jcsanz, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
The bug is still present and the behavior remains as reported. Version: 24.8.3.2 (X86_64) / LibreOffice Community Build ID: 48a6bac9e7e268aeb4c3483fcf825c94556d9f92 CPU threads: 16; OS: Windows 11 X86_64 (10.0 build 22631); UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: es-ES Calc: CL threaded -------------- Version: 25.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: deaa5dc2a4d5446cdd120236615608702598e365 CPU threads: 16; OS: Windows 11 X86_64 (10.0 build 22631); UI render: Skia/Vulkan; VCL: win Locale: es-ES (es_ES); UI: es-ES Calc: CL threaded