| 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: | 29010.1122039917@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marc Herbert | 2005-07-22 13:56:40 | getObject(<oid>) returns integer instead of LargeObject handle ? |
| Previous Message | Tom Lane | 2005-07-22 13:42:34 | Re: Timestamp Conversion Woes Redux |