On Aug 16, 2012, at 1:28 PM, Chuck Hill ch...@global-village.net wrote:
When the date data is formatted in a human readable form, that is when the
time zone comes into play. Try formatting with both the Java
SimpleDateFormat (which I recommend using in any case) and NSTimestamp
formatter.
er, this is NOT the case - all times are an hour ago.
On Aug 18, 2012, at 8:43 PM, Jesse Tayler jtay...@oeinc.com wrote:
Oddly, in a situation where I set an adjusted date on the iPhone client, it
seem to be of the correct time when that time is reported back to the iPhone
again from the
Hi Jesse,
The date with the problem is stored in a database?
We got some problems with Postgresql. Date and timezone on server was ok but
not in postgres.
We found this instruction:
ALTER DATABASE postgres SET timezone to 'Mexico/General';
That made the trick.
Hope this helps.
Miguel
oh, that might be the trouble -- I didn't think about the database encoding.
I'm using mysql, but I checked the db properties and found UTC?My server is EDT, or easter with daylight savings, for NYC. Unix reports Thu Aug 16 12:03:04 EDT 2012Should this be set to EDT? UTC is GMT right? That would
If my app output logs report the correct time, which they do:
Aug 16 12:21:17 WOMan[2002] DEBUG NSLog - === Commit Internal
Transaction
then, WO / Java have a correct timezone too.
therefore, this must be mysql?
On Aug 16, 2012, at 12:04 PM, Jesse Tayler jtay...@oeinc.com wrote:
Hi Jesse,
The problem we got with postgresql was in the period of time day light time in
U.S. begins because in Mexico begins later.
We found the datetimes stored in our database with a one hour offset during
that period, once daylight begins in Mexico everything gets normal . The server
Java and WebObjects store all times in GMT (aka UTC) internally. So if your DB
server is on UTC there should not be any conversions when the data is moved
back and forth. When the date data is formatted in a human readable form, that
is when the time zone comes into play. Try formatting with
If using postgres, you need to set the time zone before the driver loads as
well. Something like this in your application class should do
public class Application extends ERXApplication {
private static Logger log = Logger.getLogger(Application.class);
static {
My server time is off a suspicious negative one hour, which I presume to be a
daylight savings problem.
UNIX returns the date I expect.
So, I'd guess this is a Java or WO settings issue?
A long time ago, on a server far away,
there were some issues with missing timezone files used by Java
