But all types do not have similar value limits.

For example, TIMESTAMP value cannot be compared 1970 early, also cannot compare 2037 evening,

This is meant, a date for example '1968-01-01' , when should be worth as a DATETIME or DATE, it is lawful,

But it is not value of a correct TIMESTAMP! And if assign a such object,give TIMESTAMP the kind, it will is by commutation 0. When appointing date to be worth, be careful certain blemish: 　　

1, the comfortable form that allows to assign a value as string can be cheated. For example, , because of “:&The use of Rdquo; separator, value '10:11:12' may look like time value, but if be in a date,use, context will be become by the explanation as a particular year '2010-11-12' . Value '10:45:15' will be gone to by commutation '0000-00-00' , because '45' is not a lawful month. 　　　　

2, year of value that assigns with 2 digit word be faintness, because the century is sealed. MySQL uses following regulation to explain 2 year of value: Be gone to by commutation in year of value of 00-69 limits 2000-2069. Be gone to by commutation in year of value of limits 70-99 1970-1999.