Every app I have makes similar default calls. On Jul 8, 2013, at 8:34 PM, Paul Hoadley <[email protected]> wrote:
> On 09/07/2013, at 3:29 AM, Jesse Tayler <[email protected]> wrote: > >> I realize I had apparently statically set the timezone to GMT? >> >> Maybe I did this for my database?? >> >> I had this in my app constructor >> >> static { >> // Set default time zones >> //TimeZone.setDefault(TimeZone.getTimeZone("GMT")); >> //NSTimeZone.setDefaultTimeZone(NSTimeZone.getGMT()); >> } >> >> once I noticed those two line and commented them out, general <wo:str>’s >> zapped into a correct timezone on display - my component is another story >> but-- >> >> now I wonder if I’ll be storing my dates differently in the database? > > In my experience, you almost certainly want to leave those setDefault calls > _in_. The only failsafe way to deal with timezones is to set UTC everywhere > except the view layer. So, yes, you want to ensure your database is storing > timestamps as UTC (and not doing any "helpful" timezone conversions on the > way in or out), the JVM's default is UTC, and WebObjects default is UTC. The > only time you do a conversion is on the way in from the view, or on the way > out to the view, both using a user-selected or automatically-detected > timezone offset. > > > -- > Paul Hoadley > http://logicsquad.net/ > > > > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Webobjects-dev mailing list ([email protected]) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/webobjects-dev/kenlists%40anderhome.com > > This email sent to [email protected]
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
