[Libreoffice-bugs] [Bug 119135] Definition of field type as TIMESTAMP via UI for mysql table is systematically modified to DATETIME.

[bugzilla-daemon at bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=119135

--- Comment #15 from Julien Nabet <serval2412 at yahoo.fr> ---
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.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/libreoffice-bugs/attachments/20200331/fc843e0f/attachment.htm>