At 4:26 AM -0500 5/26/99, Fulajtar Pal wrote:
> I found a bug in MySQL (3.22.22). Server accepts invalid date fields
>in date and datetime fields.
>Example: 1999-02-29, 1999-02-30, 1999-02-31. And if I insert "very"
>invalid value (1999-02-32)
>the field value will be 0000-00-00, and the server doesnt give me any
MySQL's approach is that the client is responsible for providing valid
dates, and that failure to do so will produce unreliable results. The
reason for this is for server efficiency, to avoid bogging down the
server with extra validation processing.
One might prefer to have the server do a little extra processing (you
could argue this question either way), but that's how it is.
Paul DuBois, paul@stripped
Northern League Chronicles: http://www.snake.net/nl/