Skip site navigation (1) Skip section navigation (2)

Re: Strange behavior after setting timestamp field to null - A bug?

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Martti Jeenicke" <martti(dot)jeenicke(at)coremedia(dot)com>, <pgsql-jdbc(at)postgresql(dot)org>, "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
Subject: Re: Strange behavior after setting timestamp field to null - A bug?
Date: 2010-02-08 19:12:55
Message-ID: 4B700DD7020000250002F0AA@gw.wicourts.gov (view raw or flat)
Thread:
Lists: pgsql-jdbc
"Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> wrote:
 
> I was also confused by the result of changing the column to
> TIMESTAMP WITH TIME ZONE -- all timestamps were the same, but they
> were two hours later than local time and four hours earlier than
> GMT!?!
 
Never mind that last -- psql shows local time, but the Java program
is showing it as a time nine hours later than local, rather than
the six which should be GMT.  (Don't ask how I misread that before.)
 
-Kevin

In response to

pgsql-jdbc by date

Next:From: Kris JurkaDate: 2010-02-08 19:34:12
Subject: Re: Strange behavior after setting timestamp field to null - A bug?
Previous:From: Kevin GrittnerDate: 2010-02-08 19:04:40
Subject: Re: Strange behavior after setting timestamp field to null - A bug?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group