just following up again... as this /feature/ has seemingly hit us too.
On 17/01/2008, at 2:53 AM, John Pollard wrote:
We have tables with mysql DATE type fields and EO attribute types
of NSTimestamp.
After upgrading mysql from 5.0.18 to 5.0.45, the queries are no
longer matching against dates correctly.
For recent dates the date in the query sent to the database has no
time component, such as: 2008-01-01 00:00:00
But, for dates relating to British Summer Time, they appear in the
log as: 2007-08-01 01:00:00
So a 1 hour shift has been applied to the time in the query for
dates within BST.
Using mysql 5.0.18 this has/is working. With mysql 5.0.45 it no
longer works, the queries relating to BST don't match the dates
held on the datebase (just dates with no time).
Coincidentally, we recently upgraded our mysql server to 5.0.51 (and
mysql-connector-java-5.1.5 it seems) and what do you know... one-hour
shift for non-daylight savings times (here in Sydney)!
I'm seeing both that datetimes that are correctly stored in the db
are retrieved wronly and timestamps stored lose an hour.
This bug seems completely relevant... but it's not been released yet:
http://bugs.mysql.com/bug.php?id=15604
Looking further...
with regards,
--
Lachlan Deck
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
