[CAM-9498] Cannot store dates / timestamps after 2038 in MariaDB/MySQL Created: 02/Nov/18 Updated: 01/Feb/19 Resolved: 30/Jan/19
|Fix Version/s:||7.11.0, 7.11.0-alpha1|
|Type:||Bug Report||Priority:||L3 - Default|
|Reporter:||Philipp Ossler||Assignee:||Thorben Lindhauer|
|Remaining Estimate:||0 minutes|
|Time Spent:||Not Specified|
|Original Estimate:||0 minutes|
Currently, we use two different types to store a date value in a MariaDB/MySQL database: TIMESTAMP and DATETIME. The type TIMESTAMP has the limitation that it only works until 2038.
|Comment by Philipp Ossler [ 02/Nov/18 ]|
The biggest challenge is how to migrate the schema from an existing MariaDB / MySQL instance.
|Comment by Thorben Lindhauer [ 29/Jan/19 ]|
Some findings on MySQL/MariaDB timestamp handling and the jdbc driver (based on MariaDB jdbc driver 1.5.5):
|Comment by Nikola Koevski [ 30/Jan/19 ]|
Several time zone scenarios were tested for running the update script:
Application Server TZ1 + DB Server TZ2 + DB Update Session TZ2 + useLegacyDatetimeCode flag true
In all the scenarios the update was successful and the engine operation was unchanged.