Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I was studying Drupal and asked this question:

I decided to check, how the CMS will behave after the end of Unix epoch. Set my local date to 01.01.2040 and rebooted.

To my surprise, the site didn't work at all. And the reason was, that MySQL was down. I tried to connect manually and got an error:

>mysql -uroot -ppass
ERROR 2003 (HY000): Can't connect to MySQL server on 'localhost' (10061)

I am using MySQL 5.5 on Win XP. Why such strange behaviour?

share|improve this question
You're not using a WAMP in production, right?? – Camilo Martin Jan 20 '13 at 20:45
In production I am using LAMP. WAMP - on my development machine. I can look, what happens on Linux. I think, the problem remains there. – user4035 Jan 21 '13 at 10:50
I'd be curious. But not curious enough as to test it myself, so if you do test it, please tell me :) Also, it might be how your version of MySQL was distributed, maybe it's XAMPP-specific for example. If the bug is not present in LAMP, I wouldn't worry. – Camilo Martin Jan 21 '13 at 11:02
MySQL 5.1.56 works in 2040 on Linux Slackware 13.37 3.7.0-smp+ kernel. But system time was broken - was set to 1970. – user4035 Jan 21 '13 at 12:44
In cases like this I wonder what we've learnt from Y2K lol. The system time itself is broken?! – Camilo Martin Jan 21 '13 at 12:51
up vote 3 down vote accepted

The rationale is probably based on which datetime representation is easier to handle for both MySQL and the OS (in this case, Windows XP)

  • DATETIME takes up 8 bytes
  • TIMESTAMP takes up 4 bytes

Their Data and Time Ranges would differ greatly. Note further differences in the MySQL Documentation

The DATETIME type is used for values that contain both date and time parts. MySQL retrieves and displays DATETIME values in 'YYYY-MM-DD HH:MM:SS' format. The supported range is '1000-01-01 00:00:00' to '9999-12-31 23:59:59'.

The TIMESTAMP data type is used for values that contain both date and time parts. TIMESTAMP has a range of '1970-01-01 00:00:01' UTC to '2038-01-19 03:14:07' UTC.

MySQL converts TIMESTAMP values from the current time zone to UTC for storage, and back from UTC to the current time zone for retrieval. (This does not occur for other types such as DATETIME.) By default, the current time zone for each connection is the server's time. The time zone can be set on a per-connection basis. As long as the time zone setting remains constant, you get back the same value you store. If you store a TIMESTAMP value, and then change the time zone and retrieve the value, the retrieved value is different from the value you stored. This occurs because the same time zone was not used for conversion in both directions. The current time zone is available as the value of the time_zone system variable. For more information, see Section 10.6, “MySQL Server Time Zone Support”.

Since both MySQL and Windows have TimeZone Support, it was probably in MySQL's best interest to have mysqld more Windows-aware. This would probably be a secret incentive to get your MySQL database out of Windows and into Linux. (My Conspiracy Theory)

share|improve this answer
I love a good conspiracy theory! – Max Vernon Oct 2 '12 at 21:53

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.