• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag
 

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: datetime / timezone (mysql jdbc) issues
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: datetime / timezone (mysql jdbc) issues


  • Subject: Re: datetime / timezone (mysql jdbc) issues
  • From: Chuck Hill <email@hidden>
  • Date: Wed, 10 Feb 2010 22:10:36 -0800


On Feb 10, 2010, at 9:49 PM, Lachlan Deck wrote:

Hi all,

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?




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.


Chuck



So I experimented by created another field on the entity which maps to the same external field (as a read-only field) and utilising a custom class (ISHDate) with factory method 'parseDate(String)' to see what's coming in... and it's wrong there too.


I've played with various mysql jconnector params to see what happens.
...&zeroDateTimeBehavior=convertToNull
...&useGmtMillisForDatetimes=true
...&useTimezone=true&serverTimezone=Australia/Sydney
...&useLegacyDatetimeCode=true

And I've updated all the zoneinfo stuff to the latest on my system and in all the jars/frameworks. Still no good.

Further suggestions?
Cheers.

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

-- Chuck Hill Senior Consultant / VP Development

Practical WebObjects - for developers who want to increase their overall knowledge of WebObjects or who are trying to solve specific problems.
http://www.global-village.net/products/practical_webobjects








_______________________________________________
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


  • Follow-Ups:
    • Re: datetime / timezone (mysql jdbc) issues
      • From: Lachlan Deck <email@hidden>
References: 
 >datetime / timezone (mysql jdbc) issues (From: Lachlan Deck <email@hidden>)

  • Prev by Date: datetime / timezone (mysql jdbc) issues
  • Next by Date: Re: datetime / timezone (mysql jdbc) issues
  • Previous by thread: datetime / timezone (mysql jdbc) issues
  • Next by thread: Re: datetime / timezone (mysql jdbc) issues
  • Index(es):
    • Date
    • Thread