Skip site navigation (1) Skip section navigation (2)

Re: Timestamp Conversion Woes Redux

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Dave Cramer <pg(at)fastcrypt(dot)com>
Cc: Oliver Jowett <oliver(at)opencloud(dot)com>,Kris Jurka <books(at)ejurka(dot)com>,Christian Cryder <c(dot)s(dot)cryder(at)gmail(dot)com>, pgsql-jdbc(at)postgresql(dot)org
Subject: Re: Timestamp Conversion Woes Redux
Date: 2005-07-22 13:45:17
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-jdbc
Dave Cramer <pg(at)fastcrypt(dot)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

In response to

pgsql-jdbc by date

Next:From: Marc HerbertDate: 2005-07-22 13:56:40
Subject: getObject(<oid>) returns integer instead of LargeObject handle ?
Previous:From: Tom LaneDate: 2005-07-22 13:42:34
Subject: Re: Timestamp Conversion Woes Redux

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group