Description: Every time I modify a table, using BASE over Mysql, the data type of a TIMESTAMP field is modified to DATETIME. No matter how many times I have tried, when I modify the table it changes back to DATETIME. Steps to Reproduce: 1. Use as data engine MYSQL 5.7.23 2. Open BASE 3. Create a table configuring a given field as TIMESTAMP. 4. Close the table. 5. Open to edit the same table. 6. Modify it and save it. 7. The TIMESTAMP has changed to DATETIME Actual Results: 1. Use as data engine MYSQL 5.7.23 2. Open BASE and create a database 3. Create a table configuring a given field as TIMESTAMP. 4. Close the table. 5. Open to edit the same table. 6. Modify it and save it. 7. The TIMESTAMP has changed to DATETIME Expected Results: The field changes from TIMESTAMP to DATETIME and TIMESTAMP doesn't works. Reproducible: Always User Profile Reset: Yes OpenGL enabled: Yes Additional Info: Remain the configuration of TIMESTAMP unless I want to modify it.
Confirming with Version: 6.0.5.2 Build ID: 54c8cbb85f300ac59db32fe8a675ff7683cd5a16 Threads CPU : 8; OS : Mac OS X 10.13.6; UI Render : par défaut; Locale : fr-FR (fr_FR.UTF-8); Calc: group
I'm pretty sure that this is a regression, but will need to check.
My tests were made with the native mysql connector extension (MacOS).
Reproduced also with Version: 5.1.6.2 Build ID: 07ac168c60a517dba0f0d7bc7540f5afa45f0909 Threads CPU : 8; Version de l'OS :Mac OS X 10.13.6; UI Render : par défaut; Locale : fr-FR (fr_FR.UTF-8); Calc: group
Hmm, also reproduced with Version: 4.1.6.2 Build ID: 40ff705089295be5be0aae9b15123f687c05b0a maybe this bug has been around since the beginning of LO
Also reproduced with Version 3.6.7.2 (Build ID: e183d5b)
OK, so am leaning more towards the "we've always had this problem" kind of bug...
Reproduced with OOo321m18 (build9502) Setting as InheritedfromOOo
Tamás: noticing https://gerrit.libreoffice.org/#/c/55960/, thought you might be interested in this one.
Reproduced also with mysql-connector-java-5.1.36 so it isn't just limited to the native mysql connector.
Couldn't test it with native connector - isn't working here. Tested with MariaDB and mariadb-java-client-2.2.3.jar. Created a new filed for a TIMESTAMP. Saved the table, closed the database-file, reopened the database-file: The TIMESTAMP hasn't been gone. So I couldn't confirm this behavior for OpenSUSE 15, 64bit rpm Linux, MaraiaDB and Javaconnector for this MariaDB.
Hmm, inspection of the table definition created on the mysql server reveals that the timestamp field is created with the following attributes: TIMESTAMP DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP but the UI doesn't reflect this.
This has other side-effects with the jdbc-connector that cause the timestamp field to not even be displayed in the table data edit mode (double-click on table), even with the zeroDateTimeBehaviour=convertToNull flag added to the connection string.
Dear Hugo de la O, 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
On pc Debian x86-64 with master sources updated today + native mysqlc + 5.5.5-10.3.22-MariaDB-1 I could reproduce this. I wonder if it could be due to the fact that in JDBC, there's only TIMESTAMP (see https://docs.oracle.com/cd/A97337_01/ias102_otn/buslog.102/bc4j/bc_abcdatatypes.htm) so not present in https://opengrok.libreoffice.org/xref/core/offapi/com/sun/star/sdbc/DataType.idl?r=19c4d8d2 Perhaps should we use "OTHER"? 79 /** indicates that the SQL type is database-specific and 80 gets mapped to an object that can be accessed via 81 the method com::sun::star::sdbc::XRow::getObject(). 82 */ 83 const long OTHER = 1111; DATETIME and TIMESTAMP are quite similar, according to Mysql website: (https://dev.mysql.com/doc/refman/8.0/en/datetime.html) The DATETIME type is used for values that contain both date and time parts. MySQL retrieves and displays DATETIME values in 'YYYY-MM-DD hh:mm:ss' format. The supported range is '1000-01-01 00:00:00' to '9999-12-31 23:59:59'. The TIMESTAMP data type is used for values that contain both date and time parts. TIMESTAMP has a range of '1970-01-01 00:00:01' UTC to '2038-01-19 03:14:07' UTC.
I began to give a try but stuck since I get "OBJECT" in the end. Then when git grep the code, I noticed this: offapi/type_reference/offapi.idl:10204: ::com::sun::star::util::DateTime getTimestamp() raises (::com::sun::star::sdbc::SQLException); So the 2 notions timestamp and datetime seem quite mixed. => uncc myself.
Dear Hugo de la O, 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
tested this again. The following behavior appears only with the direct connector of LO: Open a table for editing, not for input date. Create a new field as timestamp. Save the table. The fieldtype won't be shown any more as timestamp, will be shown as datetime. Field properties for the new field will be NOT NULL. Open the same database with JDBC-connection. You could see the field is a timestamp field. And now: Open the database in phpMyAdmin. The new timestamp-field has been created as NOT NULL DEFAULT CURRENT_TIMESTAMP() ON UPDATE CURRENT_TIMESTAMP(). It will be possible to create such a field for a table, which has already been filled with content in some rows. The timestamp will be automatically set to the timestamp this timestamp-field has been created. So: There is no TIMESTAMP field modified to DATETIME. It is only shown as "DATETIME" in table editor with direct connection. Please test again.
(In reply to Robert Großkopf from comment #18) Hi Robert, > So: There is no TIMESTAMP field modified to DATETIME. It is only shown as > "DATETIME" in table editor with direct connection. Please test again. Yes, I think that is the real issue - the UI displays information that the field is defined as DATETIME whereas the underlying database field carries the correct definition. So, it is still a UI bug at least. Related questions would be whether or not that display value as "DATETIME" in the LO UI has other unintended consequences, e.g. how is data stored and/or entered when using the field in a form, for example, and what does it return in a query ?
Bug is still the same. TIMESTAMP field will be shown as DATETIME field with direct driver for MariaDB. Version: 24.2.4.2 (X86_64) / LibreOffice Community Build ID: 51a6219feb6075d9a4c46691dcfe0cd9c4fff3c2 CPU threads: 6; OS: Linux 6.4; UI render: default; VCL: kf5 (cairo+xcb) Locale: de-DE (de_DE.UTF-8); UI: de-DE Calc: threaded