Date and Time Data Type Syntax type_name ( fsp ) , where  type_name  is  TIME ,  DATETIME , or  TIMESTAMP , and  fsp  is the fractional seconds precision. For example: The  fsp  value, if given, must be in the range 0 to 6. A value of 0 signifies that there is no fractional part. If omitted, the default precision is 0. (This differs from the standard SQL default of 6, for compatibility with previous MySQL versions.) Any  TIMESTAMP  or  DATETIME  column in a table can have automatic initialization and updating properties; see Section 11.2.5, “Automatic Initialization and Updating for TIMESTAMP and DATETIME” . A date. The supported range is  ’1000-01-01’  to  ’9999-12-31’ . MySQL displays  DATE  values in  ’ YYYY-MM-DD ’  format, but permits assignment of values to  DATE  columns using either strings or numbers. A date and time combination. The supported range is  ’1000-01-01 00:00:00.000000’  to ’9999-12-31 23:59:59.999999’ . MySQL displays  DATETIME  values in  ’ YYYY-MM-DD hh:mm:ss [. fraction ]’  format, but permits assignment of values to  DATETIME  columns using either strings or numbers. An optional  fsp  value in the range from 0 to 6 may be given to specify fractional seconds precision. A value of 0 signifies that there is no fractional part. If omitted, the default precision is 0. Automatic initialization and updating to the current date and time for  DATETIME  columns can be specified using  DEFAULT  and  ON UPDATE  column definition clauses, as described in Section 11.2.5, “Automatic Initialization and Updating for TIMESTAMP and DATETIME” . A timestamp. The range is  ’1970-01-01 00:00:01.000000’  UTC to  ’2038-01-19 03:14:07.999999’  UTC.  TIMESTAMP  values are stored as the number of seconds since the epoch ( ’1970-01-01 00:00:00’  UTC). A  TIMESTAMP  cannot represent the value  ’1970-01-01 00:00:00’  because that is equivalent to 0 seconds from the epoch and the value 0 is reserved for representing  ’0000-00-00 00:00:00’ , the “zero” TIMESTAMP  value. An optional  fsp  value in the range from 0 to 6 may be given to specify fractional seconds precision. A value of 0 signifies that there is no fractional part. If omitted, the default precision is 0. The way the server handles  TIMESTAMP  definitions depends on the value of the explicit_defaults_for_timestamp  system variable (see Section 5.1.8, “Server System Variables” ). If  explicit_defaults_for_timestamp  is enabled, there is no automatic assignment of the DEFAULT CURRENT_TIMESTAMP  or  ON UPDATE CURRENT_TIMESTAMP  attributes to any  TIMESTAMP column. They must be included explicitly in the column definition. Also, any  TIMESTAMP  not explicitly declared as  NOT NULL  permits  NULL  values. If  explicit_defaults_for_timestamp  is disabled, the server handles  TIMESTAMP  as follows: Unless specified otherwise, the first  TIMESTAMP  column in a table is defined to be automatically set to the date and time of the most recent modification if not explicitly assigned a value. This makes TIMESTAMP  useful for recording the timestamp of an  INSERT  or  UPDATE  operation. You can also set 2023 •  TIMESTAMP[( fsp )] •  DATETIME[( fsp )] •  DATE CREATE TABLE t1 (t TIME(3), dt DATETIME(6), ts TIMESTAMP(0));