Bug #27569 TIMESTAMP should end in 2038, not 2037
Submitted: 1 Apr 2007 7:30 Modified: 1 Apr 2007 23:17
Reporter: Glenn Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Documentation Severity:S3 (Non-critical)
Version:5.0 OS:
Assigned to: Paul DuBois CPU Architecture:Any

[1 Apr 2007 7:30] Glenn 
Description:
Section 11.1.2 of the MySQL Reference Manual says that the range of a TIMESTAMP is "partway through the year 2037".  But unless I miss my guess, you're using the usual 32-bit UNIX timestamp as the representation, and that range runs out instead in early 2038:

2147483647 = Tue Jan 19 03:14:07 2038 GMT 

Please correct the documentation, as it's a bit confusing when comparing against other sources.

How to repeat:
Read the manual.  Compare against:  http://en.wikipedia.org/wiki/Year_2038_problem

Suggested fix:
Change the documentation to refer to "the year 2038".
[1 Apr 2007 7:59] Valeriy Kravchuk 
Thank you for a reasonable documentation request. This page, http://dev.mysql.com/doc/refman/5.0/en/date-and-time-type-overview.html, should be corrected.
[1 Apr 2007 23:17] Paul DuBois 
Thank you for your bug report. This issue has been addressed in the documentation. The updated documentation will appear on our website shortly, and will be included in the next release of the relevant products.