Re: Timestamp Conversion Woes Redux - Mailing list pgsql-jdbc

From Tom Lane
Subject Re: Timestamp Conversion Woes Redux
Date
Msg-id 29010.1122039917@sss.pgh.pa.us
Whole thread Raw
In response to Re: Timestamp Conversion Woes Redux  (Dave Cramer <pg@fastcrypt.com>)
List pgsql-jdbc
Dave Cramer <pg@fastcrypt.com> writes:
> On 21-Jul-05, at 8:54 PM, Tom Lane wrote:
>> The more I think about this, the more I think that the correct
>> solution
>> must include having the driver set TimeZone = UTC (and complain if the
>> app tries to change it).

> This really isn't an option. We can't impose limits on the
> application like this.

Why not?  Why should the application care what the server's timezone is?
Especially in a context where it's up to the driver to manage all these
conversion issues...

            regards, tom lane

pgsql-jdbc by date:

Previous
From: Tom Lane
Date:
Subject: Re: Timestamp Conversion Woes Redux
Next
From: Marc Herbert
Date:
Subject: getObject() returns integer instead of LargeObject handle ?