For the DATE and
DATETIME range descriptions,
“supported” means that although earlier values
might work, there is no guarantee.

MySQL permits fractional seconds for
TIME,
DATETIME, and
TIMESTAMP values, with up to
microseconds (6 digits) precision. To define a column that
includes a fractional seconds part, use the syntax
type_name(fsp),
where type_name is
TIME,
DATETIME, or
TIMESTAMP, and
fsp is the fractional seconds
precision. For example:

CREATE TABLE t1 (t TIME(3), dt DATETIME(6));

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.

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.

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.

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.

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 any TIMESTAMP column
to the current date and time by assigning it a
NULL value, unless it has been defined
with the NULL attribute to permit
NULL values.

Automatic initialization and updating to the current date
and time can be specified using DEFAULT
CURRENT_TIMESTAMP and ON UPDATE
CURRENT_TIMESTAMP column definition clauses. By
default, the first TIMESTAMP
column has these properties, as previously noted. However,
any TIMESTAMP column in a
table can be defined to have these properties.

A time. The range is '-838:59:59.000000'
to '838:59:59.000000'. MySQL displays
TIME values in
'HH:MM:SS[.fraction]' format, but permits
assignment of values to TIME
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.

The SUM() and
AVG() aggregate functions do not
work with temporal values. (They convert the values to numbers,
losing everything after the first nonnumeric character.) To work
around this problem, convert to numeric units, perform the
aggregate operation, and convert back to a temporal value.
Examples:

The MySQL server can be run with the
MAXDB SQL mode enabled. In
this case, TIMESTAMP is
identical with DATETIME. If
this mode is enabled at the time that a table is created,
TIMESTAMP columns are created
as DATETIME columns. As a
result, such columns use
DATETIME display format, have
the same range of values, and there is no automatic
initialization or updating to the current date and time. See
Section 5.1.8, “Server SQL Modes”.

Note

As of MySQL 5.7.22, MAXDB is
deprecated. It will be removed in a future version of MySQL.

To select from a date range with MySql timestamp using the unix_timestamp, then display in human readable format. This is great with php, when you use drop down date ranges.The $starttime and $endtime are varibals that I passed in my php script. I also made the varibles into a unix_timestamp in php using the mktime()

select date_format(FieldWithMysqlTimestamp1, '%b-%d-%Y') as Field1, Field2, Field3, date_format(FieldWithMysqlTimestamp2, '%b-%d-%Y') as Field4 from TableName where unix_timestamp(FieldWithMysqlTimestamp1) between $starttime and $endtime