Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
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: Mon, 08 Feb 2010 13:12:55 -0600
- Message-id: <4B700DD7020000250002F0AA@gw.wicourts.gov> <text/plain>
"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
- References:
- Strange behavior after setting timestamp field to null - A bug?
- From: Jeenicke, Martti
- Re: Strange behavior after setting timestamp field to null - A bug?
- From: Kevin Grittner
- Strange behavior after setting timestamp field to null - A bug?
- Prev by Date: Re: Strange behavior after setting timestamp field to null - A bug?
- Next by Date: Re: Strange behavior after setting timestamp field to null - A bug?
- Previous by thread: Re: Strange behavior after setting timestamp field to null - A bug?
- Next by thread: Re: Strange behavior after setting timestamp field to null - A bug?
- Indexes: