Details
-
Task
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Duplicate
-
None
Description
Currently, functions like UNIX_TIMESTAMP() return 0 after 3:14:07 UTC on Jan 19, 2038. I am not sure what other functions are not compliant. Ideally, this should be fixed by using 64-bit time in seconds on all platforms, but it should at a minimum use 64-bit time on 64-bit platforms.
Attachments
Issue Links
- duplicates
-
MDEV-32188 make TIMESTAMP use whole 32-bit unsigned range
- Closed
- relates to
-
MDEV-16135 Service does not start if date set beyond Y2038
- Closed
-
MDEV-26736 UNIX_TIMESTAMP doesn't work beyond 2038 (aka y2.038k)
- Closed