[MDEV-9444] MariaDB needs to be Y2038-compliant Created: 2016-01-21  Updated: 2023-09-18  Resolved: 2016-02-05

Status: Closed
Project: MariaDB Server
Component/s: OTHER
Fix Version/s: N/A

Type: Task Priority: Major
Reporter: John Lange Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None

Issue Links:
Duplicate
duplicates MDEV-32188 make TIMESTAMP use whole 32-bit unsig... In Testing
Relates
relates to MDEV-26736 UNIX_TIMESTAMP doesn't work beyond 20... Closed

 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.


Generated at Thu Feb 08 07:34:43 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.