Re: Timestamp Conversion Woes Redux

On 20-Jul-05, at 4:44 PM, Christian Cryder wrote:

> On 7/20/05, Dave Cramer <pg@fastcrypt.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
>
>