Bug #70177 Increase TIMESTAMP range to be able to store values for year 2038 and beyond
Submitted: 28 Aug 2013 18:28 Modified: 7 Jul 2016 2:01
Reporter: Dimitriy A Email Updates:
Status: Open Impact on me:
None 
Category:MySQL Server Severity:S4 (Feature request)
Version:MySQL 5.1 and up OS:Any
Assigned to: CPU Architecture:Any
Tags: Data Type, range, timestamp

[28 Aug 2013 18:28] Dimitriy A 
Description:
TIMESTAMP data type range is limited to the following:
The range is '1970-01-01 00:00:01.000000' UTC to '2038-01-19 03:14:07.999999' UTC.

Please increase the range so that it is able to store values for the full year of 2038 and beyond. Ideally adding a century or more to the range.

Having this feature implemented early on would allow for smoother migration and will not be a last minute upgrade for organizations when year 2038 comes.

How to repeat:
N/A

Suggested fix:
N/A
[7 Jul 2016 2:01] Dimitriy A 
We are slowly getting closer to 2038. What's the reason for filing this as a feature request and not a bug? When would it become a bug? If it is 2038 then it is quite late for many people. Thanks.
[22 Mar 2017 9:21] Daniël van Eeden 
I think this is a duplicate of:
Bug #12654 	64-bit unix timestamp is not supported in MySQL functions