From: | Richard Emberson <emberson(at)phc(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: now() AT TIME ZONE 'GMT'; |
Date: | 2002-04-09 15:14:08 |
Message-ID: | 3CB30540.2151BD78@phc.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
Tom Lane wrote:
> Richard Emberson <emberson(at)phc(dot)net> writes:
> > If I want a column to have a default TIMESTAMP of 'now' but not in PST
> > timezone but GMT,
>
> It strikes me that you have a conceptual error. Type TIMESTAMP (ie,
I guess so. So it is during the retrieval of a timestamp using jdbc, where
the timestamp
is converted into a java.sql.Timestamp that it gets converted to a local
timezone.
So I will have to use the jdbc access method that preserves (actually where
one can
set the desired timezone) the timezone.
Richard
From | Date | Subject | |
---|---|---|---|
Next Message | Patrick Welche | 2002-04-09 15:22:50 | Re: numeric test on RiscPC |
Previous Message | Papp, Gyozo | 2002-04-09 14:56:40 | Re: SPI_execp() failed in RI_FKey_cascade_del() |
From | Date | Subject | |
---|---|---|---|
Next Message | Mikhail Terekhov | 2002-04-09 17:09:29 | Re: notification: pg_notify ? |
Previous Message | Tom Lane | 2002-04-09 13:20:22 | Re: timeout implementation issues |