JDBC still relies on java.sql.Timestamp, etc, which uses the system's time zone when saving and loading data. Usually the easiest solution is to set the default time zone to UTC by adding a VM argument -Duser.timezone=UTC
Then when you need to display date times you can choose a different time zone for display purposes explicitly. On Thu, Nov 14, 2013 at 10:51 PM, Jeffrey Schmitz <[email protected]>wrote: > Hello List, > A simple question about a time value (as if any quesiton about > webobjects and time is simple :-)), I have a field I've defined using the > jodaLocalDateTime prototype. I was assuming that if I save the value > 2013-11-14T12:00:00.000 > to my EO, the database would save exactly that, using 12:00:00 for the > time. However when I go to the database, the actual time saved is 6:00:00, > so obviously it is assuming the time I'm saving is in Greenwich time and > converting it to Local time. By the name, maybe that makes sense, but I > was thinking LocalTime meant time zone free. > > What makes this more maddening is that when I go to display the time from > my EO, it displays it as 6:00:00, so in essence, it's doing the conversion > on the save, but not on the retrieve. What am I missing here? > > Thanks! > Jeff > > _______________________________________________ > 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/johnthuss%40gmail.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]
