Mysql timestamp overflow problem

As we all know, the timestamp is the number of seconds since January 1, January 1, 1970 (00: 00: 00GMT. It is also known as the Unix timestamp (UnixTimestamp ). Mysql also provides timestamp functions, such as unix_timestamp () and from_unixtime (). Currently, the general timestamp is a 32-bit unsigned integer, which indicates that the timestamp will

As we all know, the timestamp is the number of seconds since January 1, January 1, 1970 (00:00:00 GMT. It is also called Unix Timestamp ). Mysql also provides timestamp functions, such as unix_timestamp () and from_unixtime (). Currently, the general timestamp is a 32-bit unsigned integer, which indicates that the timestamp will

As we all know, the timestamp is the number of seconds since January 1, January 1, 1970 (00:00:00 GMT. It is also called Unix Timestamp ).

Mysql also provides timestamp functions, such as unix_timestamp () and from_unixtime ().
Now the General timestamp seems to be a 32-bit unsigned integer, which indicates that the timestamp will overflow over time. In fact, the timestamp range is until January 1, 2038.

What if your unix_timestamp () function lock gets in 2039? It is very easy to adjust your system time to 2039, and then restart your mysql service. The following prompt box is displayed:

For example, on the mysql command line, enter select UNIX_TIMESTAMP ('2017-01-01 ');