Comparison between Datetime and Timestamp in Mysql _ MySQL

This article mainly introduces the comparison of Datetime and Timestamp in Mysql. This article summarizes their similarities and differences and the introduction of time formats, for more information, see the three types of date, datetime, and timestamp used in mysql to indicate time (if int is used, four types, the similarities and differences between the three types are compared below.

Similarities

Can be used to indicate the time
Are displayed as strings

Differences

1. as the name suggests, date only represents the date in the form of 'yyyy-MM-DD ', datetime represents the date plus time in the form of 'yyyy-MM-DD HH: mm: SS', timestamp and datetime display form is the same.
2. the time range that date and datetime can represent is '2017-01-01 'to '2017-12-31'. timestamp is limited by 32-bit int type, it indicates the UTC time between '2017-01-01 00:00:01 'and '2017-01-19 03:14:07.
3. when mysql stores the timestamp type, it converts the time to UTC time, and then restores it to the current time zone when reading the data. If you have stored a value of the timestamp type and modified the mysql time zone, you will get an error time when you read the value again. This does not happen in date and datetime.
4. the timestamp type provides the automatic update function. you only need to set its default value to CURRENT_TIMESTAMP.
5. except that date is retained to the day, datetime and timestamp are retained to the second, while millisecond is ignored.

Time format

Mysql provides a relatively loose time string format for addition, deletion, modification, and query. Refer to the iso time format. generally, it is used to writing '2017-06-05 16:34:18 '. However, you can also name it '13-6-5 ', but this is easy to cause confusion. for example, mysql also treats '13: 6: 5' as year, month, and day, while '13: 16: 5' is considered incorrect by mysql. a warning is given and the value stored in the database is '2017-00-00 00:00:00 '.

The manual also specifically mentions a situation where the value of the current year is 0 ~ 69, mysql considers it as 2000 ~ 2069, and 70 ~ 99 is considered as 1970 ~ 1999. I feel like it is a superfluous thing.

In short, using the 'yyyy-MM-DD HH: mm: SS' format will always be fine.