 |  |
| |
Though MySQL is somewhat forgiving on the input format, you should actually attempt to format all date values in your applications in MySQL's native format to avoid any confusion. MySQL always expects the year to be the left-most element of a date format. If you assign an illegal value in an SQL operation, MySQL will insert a zero for that value.
MySQL will also perform automatic conversion of date and time values to integer values when used in an integer context.
| DATE |
DATE
YYYY-MM-DD (2001-01-01)
3 bytes
Stores a date in the range of January 1, 1000 ('1000-01-01') to December 31, 9999 ('9999-12-31') in the Gregorian calendar.
| DATETIME |
DATETIME
YYYY-MM-DD hh:mm:ss (2001-01-01 01:00:00)
8 bytes
Stores a specific time in the range of 12:00:00 AM, January 1, 1000 ('1000-01-01 00:00:00') to 11:59:59 P.M., December 31, 9999 ('9999-12-31 23:59:59') in the Gregorian calendar.
| TIME |
TIME
hh:mm:ss (06:00:00)
3 bytes
Stores a time value in the range of midnight ('00:00:00') to one second before midnight ('23:59:59').
| TIMESTAMP |
TIMESTAMP[(display_size)]
YYYYMMDDhhmmss (20010101060000)
4 bytes
A simple representation of a point in time down to the second in the range of midnight on January 1, 1970, to one minute before midnight on December 31, 2037. Its primary utility is keeping track of table modifications. When you insert a NULL value into a TIMESTAMP column, the current date and time are inserted instead. When you modify any value in a row with a TIMESTAMP column, the first TIMESTAMP column will be automatically updated with the current date and time.
| YEAR |
YEAR
YYYY (2001)
1 byte
Stores a year of the Gregorian calendar in the range of 1900 to 2155.
|  | |
| 16.2. String Data Types |  | 16.4. Complex Data Types |
Copyright © 2003 O'Reilly & Associates. All rights reserved.