Re: datetime / timezone (mysql jdbc) issues
Re: datetime / timezone (mysql jdbc) issues
- Subject: Re: datetime / timezone (mysql jdbc) issues
- From: Lachlan Deck <email@hidden>
- Date: Thu, 11 Feb 2010 17:14:03 +1100
On 11/02/2010, at 5:10 PM, Chuck Hill wrote:
> On Feb 10, 2010, at 9:49 PM, Lachlan Deck wrote:
>
>> I've been debugging a problem we've got where the fetched timestamp is 1 hour out for times that fall after (or close after) the date when day light savings comes off.
>
> That seems pretty normal for Java where a day is 24 * 60 * 60 * 1000 milliseconds, not a day like we usually think of it. If I don't care about the time, I just set it to 12:00 noon. So when Java adjusts the time, it is 11AM or 1PM, but at least on the correct day. Is that what you are seeing? Or am I misunderstanding the problem?
Yes. This is a timestamp / datetime (not a date only value).
The correct value should be 4pm Sydney time. But for this last one it's 5pm.
>> Viewing the data in mysql the times are correct for Sydney (unfortunately the deployment db is not in UTC but Australia/Sydney time... out of my hands). When fetching a list of records all of them have the same endTimestamp value .. but once we have an NSTimestamp the last record which falls over the boundary is wrong.
>
> I am having a hard time parsing that last sentence.
I'll try again :)
A list of records in the database with a field called 'endTimestamp' all have a value where their time-part == 4pm Sydney time. Once fetched, one of them is wrong.
with regards,
--
Lachlan Deck
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden