Spec-Zone .ru
спецификации, руководства, описания, API
|
Date values with two-digit years are ambiguous because the century is unknown. Such values must be interpreted into four-digit form because MySQL stores years internally using four digits.
For DATETIME
, DATE
, and TIMESTAMP
types, MySQL interprets dates specified with ambiguous year values
using these rules:
Year values in the range 00-69
are converted to 2000-2069
.
Year values in the range 70-99
are converted to 1970-1999
.
For YEAR
, the rules are the same, with this exception: A numeric 00
inserted into YEAR(4)
results in 0000
rather than 2000
. To specify zero for YEAR(4)
and have it be interpreted as 2000
, specify it
as a string '0'
or '00'
.
Remember that these rules are only heuristics that provide reasonable guesses as to what your data values mean. If the rules used by MySQL do not produce the values you require, you must provide unambiguous input containing four-digit year values.
ORDER BY
properly sorts YEAR
values that have two-digit years.
Some functions like MIN()
and MAX()
convert a YEAR
to a number. This means that a value with a two-digit year does not work properly with these functions. The fix
in this case is to convert the YEAR
to four-digit year format.