| From: | Dave Cramer <pg(at)fastcrypt(dot)com> |
|---|---|
| To: | Christian Cryder <c(dot)s(dot)cryder(at)gmail(dot)com> |
| Cc: | Kris Jurka <books(at)ejurka(dot)com>, John R Pierce <pierce(at)hogranch(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Oliver Jowett <oliver(at)opencloud(dot)com>, pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: Timestamp Conversion Woes Redux |
| Date: | 2005-07-20 20:56:42 |
| Message-ID: | 3AD13B6B-08B7-4B6C-9346-08AF48F68E49@fastcrypt.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
On 20-Jul-05, at 4:44 PM, Christian Cryder wrote:
> On 7/20/05, Dave Cramer <pg(at)fastcrypt(dot)com> wrote:
>
>> I think using the same time zone as the server is the only way to go:
>>
>
> How does this prevent the DST munging issue, where a zoneless time
> (eg. 04-03-2005 1:22 AM) is read from the DB and then re-written? What
> is to keep it being from being rewritten as 2:22 AM?
We still have the crossover to deal with
>
>
>> Kris has proposed a patch which would set the servers time zone to
>> the JVM when the connection is started
>>
>
> What happens when someone writes a client server app, and one client
> connects from timezone A, and another client connects from timezone B,
> and the server itself is running in timezone C?
>
Setting the servers time zone only sets the time zone for that client.
> Christian
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Cramer | 2005-07-20 22:04:54 | Re: Custom types in Postgres, JDBC |
| Previous Message | Christian Cryder | 2005-07-20 20:52:21 | Custom types in Postgres, JDBC |