mysql 32位整数,为什么MySQL unix时间不能超过32位无符号整数限制？

最新推荐文章于 2022-11-18 17:41:04 发布

样文理

最新推荐文章于 2022-11-18 17:41:04 发布

阅读量154

点赞数

文章标签： mysql 32位整数

mysql> SELECT FROM_UNIXTIME(2145916799), FROM_UNIXTIME(2145916800), POW(2,32-1)-1, 2145916799 - POW(2,32-1)-1;

+---------------------------+---------------------------+---------------+----------------------------+

| FROM_UNIXTIME(2145916799) | FROM_UNIXTIME(2145916800) | POW(2,32-1)-1 | 2145916799 - POW(2,32-1)-1 |

+---------------------------+---------------------------+---------------+----------------------------+

| 2037-12-31 18:59:59 | NULL | 2147483647 | -1566850 |

+---------------------------+---------------------------+---------------+----------------------------+

1 row in set (0.00 sec)

mysql>

The first field is the highest possible value I can give to FROM_UNIXTIME. The next field is that value plus one which returns NULL. The third field is the highest possible value for an unsigned 32 bit int. The final value is the difference between the highest possible UNIXTIME and the highest possible int which is a little over 18 days worth of seconds. It appears that it stops at the end of 2037 in the local timezone. Any ideas why? Is that a natural breaking point in one of the calculations? Is that just an arbitrary limit in mysqld?

解决方案

normally unix timestamp range is from January 1st 1970 to December 31st 2037

for more information have a look at http://en.wikipedia.org/wiki/Year_2038_problem