Bug #52693 | Cannot insert the maximum timestamp value into a timestamp column | ||
---|---|---|---|
Submitted: | 8 Apr 2010 15:11 | Modified: | 8 Apr 2010 20:53 |
Reporter: | Tom Groszko | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server: Data Types | Severity: | S3 (Non-critical) |
Version: | 5.1 | OS: | Windows |
Assigned to: | CPU Architecture: | Any | |
Tags: | maximum timestamp |
[8 Apr 2010 15:11]
Tom Groszko
[8 Apr 2010 16:50]
Sveta Smirnova
Thank you for the report. Please provide output of SHOW VARIABLES LIKE 'time_zone' and if this is SYSTEM timezone indicate which timezone uses your OS.
[8 Apr 2010 18:23]
Tom Groszko
SHOW VARIABLES LIKE 'time_zone' ; time_zone SYSTEM I am not sure what you mean by "indicate which timezone uses your OS". What command do I issue to show this? I am in the Eastern United States timezone which is currently using daylight savings time. The documentation for this value does not seem to care where in the world I am. It gives two unqualified values of which only the first works.
[8 Apr 2010 18:30]
Sveta Smirnova
Thank you for the feedback. Eastern United States timezone is not UTC. See http://dev.mysql.com/doc/refman/5.1/en/timestamp.html about how TIMESTAMP columns are affected by timezones. So this is not a bug.
[8 Apr 2010 20:53]
Tom Groszko
Thanks that clears it up.