On Sat, 29 May 1999, Jim Faucette wrote:
>
> Data entry exception coding is not the same as the Y2K storage issue.
That true, I agree with you.
>
> 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.
1. As I think, one of very primitive program that manage the date-time,
can be able to check these ranges. Why MySQL could not?
2. If MySQL can't be able to check it, I don't know why do they want to
build DATE DATETIME etc.. column type? Because, I can use CHAR VARCHAR
instead and I will check date entry before I type it.
>
> So 19991299 would be accepted just as 19990231 is now.
I think 00000000 is better, because I will know I did wrong.
Best regards,
----------------
Quang D. Nguyen (nguyen@stripped)
"General Protection Fault"(R) is Registered Trademark of Micro$oft
