Created attachment 125208 [details] Run the SQL-code to create DB, change the user and have a look at the table A special problem with JDBC-connection an MariaDB/MySQL-DB. Create a table in MySQL/MariaDB. Set one datetime-field to DEFAULT NULL ON UPDATE CURRENT_TIMESTAMP. This field won't be shown if opening the table with Base, if connected to the DB with JDBC. Works right with direct connection. This field won't be shown in a query also. Added an example database and the SQL-code to create the database and table. There must be changed the user to connect to the database. This code will be executed: CREATE TABLE IF NOT EXISTS `table` ( `ID` mediumint(7) NOT NULL, `Name` varchar(100) DEFAULT NULL, `DateTime_Default` datetime DEFAULT CURRENT_TIMESTAMP, `DateTime_OnUpdateDefault` datetime DEFAULT NULL ON UPDATE CURRENT_TIMESTAMP, `Field5` varchar(100) DEFAULT NULL ) ENGINE=InnoDB DEFAULT CHARSET=utf8; Five fields. Four fields will be shown, when opening the table in LO-Base for input values. Five fields will be shown, when opening the table for editing the structure of the table.
Created attachment 125217 [details] Query should contain 5 fields - only 4 fields will be shown. Fields with "ON UPDATE CURRENT_TIMESTAMP" aren't shown in queries. You could only see the content of this fields, if you create a view of such a query.
Hi Robert, I will test, but am hasarding a guess that this is linked to bug 85190
I wouldn't be too surprised if the JDBC driver hides that column by default. Which version of which JDBC driver are you using? I see in the changelog of the MySQL one: 09-06-12 - Version 5.1.22 - Fix for Bug#63800, getVersionColumns() does not return timestamp fields; always empty. Added support of ON UPDATE CURRENT_TIMESTAMP for TIMESTAMP and DATETIME fields. I suppose you are using something more recent than that?
Confirming on Version: 5.1.3.2 Build ID: 644e4637d1d8544fd9f56425bd6cec110e49301b CPU Threads: 2; OS Version: Mac OS X 10.11.4; UI Render: default; Locale: fr-FR (fr.UTF-8) with mysql JDBC connector 5.1.39
I see the same issue with Version: 4.1.4.2 Build ID: 0a0440ccc0227ad9829de5f46be37cfb6edcf72 and JDBC connector 5.1.34
I also see the same problem in LibreOffice 3.3.0 OOO330m19 (Build:6) tag libreoffice-3.3.0.4 with JDBC connector 5.1.34
I'd appreciate if someone could check with another JDBC-using application, such as e.g. sqlline . It would tell us whether the column is hidden by the JDBC driver or if LibreOffice "loses" it.
The SQL DDL typed in from the mysql command line fails to create a table in my installed version of mysql (5.5.25a) on OSX: `DateTime_Default` datetime DEFAULT CURRENT_TIMESTAMP, `DateTime_OnUpdateDefault` datetime DEFAULT NULL ON UPDATE CURRENT_TIMESTAMP
OK, so I'm using a 5.7 client to connect to a 5.5 server and of course strict mode is enabled by default in 5.7 client sessions, which excludes zero date values, hences the failure of the create setting - sigh...
** 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 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 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: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Tested this one again with Version: 6.0.3.2 Build-ID: 8f48d515416608e3a835360314dac7e47fd0b821 CPU-Threads: 4; BS: Linux 4.4; UI-Render: Standard; VCL: kde4; Gebietsschema: de-DE (de_DE.UTF-8); Calc: group and MariaDB Connector/J 2.2.3 Stable 2018-03-14 All fields were shown, works as expected. I will set this one to WORKSFORME.