Quang D. Nguyen wrote:
> On Sat, 29 May 1999, Paul DuBois wrote:
> > What result are you expecting?
> 0000-00-00 like if you insert .. values ('1999-12-35');
> How do you think about that? If MySQL do not able to manage this problem,
> how can it manage the Y2K-t? I think this is more simple than other.
Data entry exception coding is not the same as the Y2K storage issue.
I do agree that MySQL's handling of date entries is not consistant. The
developers' position is that exception coding should be the users
responsibility. If MySQL did NO date range checks on date entries
(instead of the few it does now), then maybe this question would stop
being asked so often.
So 19991299 would be accepted just as 19990231 is now.