List:General Discussion« Previous MessageNext Message »
From:Sasha Pachev Date:May 26 1999 3:58pm
Subject:Re: y2k bug in MySQL
View as plain text  
Paul DuBois wrote:
> 
> At 4:26 AM -0500 5/26/99, Fulajtar Pal wrote:
> >Hi,
> >  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
> >error message.
> 
> 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/
> 

And if you like it to do validation for you, you have
the sources...


-- 
Sasha Pachev
http://www.sashanet.com/ (home)
http://www.direct1.com/ (work)
Thread
y2k bug in MySQLFulajtar Pal26 May
  • Re: y2k bug in MySQLPaul DuBois26 May
    • Re: y2k bug in MySQLSasha Pachev26 May