Created attachment 59629 [details] Screenshot of the date display issue LibreOffice Base does not display date fields properly with the native driver included in LibreOffice 3.5.2. Date fields are allways displayed as 01/01/1800 (DD/MM/YYYY). This issue not only happens with null values, but also when the date fields are actually set to a proper value. Screenshot provided.
Hi Rainer, do you understand, waht reporter means?
(In reply to comment #1) > Hi Rainer, > > do you understand, waht reporter means? Pretty simple IMHO : 1) Create an ODB file which connects to a postgresql db via the native postgres connector now included in LO by default. 2) Load a table containing dates, or create one, and check the result displayed : - in the table itself - in a form (as the user has provided a snapshot in colour, I'm betting that this is a form display and not the Table view display). 3) Check to see whether problem exists. 4) Also check to see whether it is not a duplicate of some other database form display problems (I seem to recall that there is one already). Alex
Looking at the screenshot again, it is definitely a form. Alex
Adding link to fdo#36858 because I think that it is possibly the same underlying problem. Alex
I get this only for NULL dates
Actually, I get that only on newly inserted rows, and only for the fields that were not filled in. For integer fields, I get "zero".
I've stumbled over something similar in a form: I have two tables, "accounts" and "transactions", and a form showing both (with the latter being limited to the currently selected account, which is a foreign key in the transactions table. When I insert a new account, it is inserted properly, but the account ID (which is set by Postgres from a sequence) is assumed to be 0. When I then attempt to insert a transaction for that account, the INSERT fails because 0 is not a valid account ID and so the foreign key constraint is not met. Closing and reopening the form rereads the ID, and allows me to insert transactions.
Adding self to CC if not already on
** Please read this message in its entirety before responding ** 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 on a currently supported version of LibreOffice (5.0.4 or later) https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) http://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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2016-01-17
** Please read this message in its entirety before responding ** 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 on a currently supported version of LibreOffice (5.2.5 or 5.3.0 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) http://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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170306
Any update with 6.0.5 + the fact that tdf#36858 has been fixed?
(In reply to Julien Nabet from comment #11) > Any update with 6.0.5 + the fact that tdf#36858 has been fixed? Dear Luc MASSENAUX, Alex Thurgood, Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ?
No repro for me with: Version: 5.4.7.2 Build ID: c838ef25c16710f8838b1faec480ebba495259d0 Threads CPU : 8; OS : Mac OS X 10.13.5; UI Render : par défaut; Locale : fr-FR (fr_FR.UTF-8); Calc: group