Timestamp Expiration Issue

Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: timestamp到期问题

| username: TiDBer_pkQ5q1l0

[TiDB Usage Environment] Production Environment
[TiDB Version]
The timestamp will expire in 2038, which is 15 years from now. Is there any new data type that can replace the timestamp data type?
[Resource Configuration]
[Attachment: Screenshot/Log/Monitoring]

| username: tidb菜鸟一只 | Original post link

MySQL has supported the new data type datetime(6) since version 5.6.4. This type provides microsecond-level timestamp precision and supports a wide range of time, from as early as the year 1000 to as late as the year 9999, which is much broader than the range supported by the timestamp type. Therefore, datetime(6) can serve as an alternative to timestamp, better supporting long-term timestamp calculations in applications.

| username: TiDBer_pkQ5q1l0 | Original post link

Thank you for the explanation.

| username: system | Original post link

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.