See, for the UK, on that date, 2am to 2:59 inclusive do not officially
exist - hence, 3am to 3:59 for GMT+1, etc. I couldn't quite figure why 3am
was being rejected until now. I'm impressed that MySQL knows that {:v)-- Jason Teagle [EMAIL PROTECTED] > -----Original Message----- > From: Ricardas.S [mailto:[EMAIL PROTECTED] > Sent: 21 March 2006 14:31 > To: [EMAIL PROTECTED] > Subject: Re: Timestamp problem in mysql5.0.18 > > > Yes, I think you are right, it should be the main reason of > insert failure. > Thank you for good idea. > > Ricka > > ----- Original Message ----- > From: "Jason Teagle" <[EMAIL PROTECTED]> > To: "Ricardas.S" <[EMAIL PROTECTED]> > Sent: Tuesday, March 21, 2006 14:55 > Subject: RE: Timestamp problem in mysql5.0.18 > > > > > All other date or hour values I tried, works good, but this one > > > is not accepted. UPDATE statement behaves the same. > > > Server time zone is GMT+2. > > > I tried 5.0.18nt and two linux versions, result is the same. > > > I tried to change time zone, and noticed that mysql server does > > > not accept 2006-03-26 date with hour values which are equals GMT > > > offset + 1. > > > When I tried with ALLOW_INVALID_DATES option enabled, then server > > > simply changes hour upward to 04. > > > > > > Is it mysql bug? > > > > I believe that the clocks go forward in the UK (and possibly other > > countries) on the 26th - 2am suddenly becomes 3am. I wonder if > this is part > > of the problem? Seems a bit of a coincidence, especially as you > say it went > > to 4am. > > > > -- > > Jason Teagle > > [EMAIL PROTECTED] > > > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
