| From: | Dave Cramer <pg(at)fastcrypt(dot)com> |
|---|---|
| To: | Oliver Jowett <oliver(at)opencloud(dot)com> |
| Cc: | 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-21 00:37:40 |
| Message-ID: | 59DE5C3D-585A-4DF2-BF77-8D9669D50335@fastcrypt.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
On 20-Jul-05, at 8:16 PM, Oliver Jowett wrote:
> Kris Jurka wrote:
>
>>
>> On Thu, 21 Jul 2005, Oliver Jowett wrote:
>>
>>
>>> Aside from the issues that others have raised, I was worried about
>>> existing code that does *not* use PreparedStatement. (probably
>>> with good
>>> reason given this discussion!)
>>>
>>> I really don't think the driver should be touching TimeZone :/
>>>
>>
>> You might appreciate this archived message...
>>
>> http://archives.postgresql.org/pgsql-jdbc/2004-12/msg00169.php
>>
>
> Heh, good point :-)
>
> Of course there are no broken applications out there! ;-)
>
> I still think touching TimeZone is asking for trouble -- we've got no
> guarantees that the Java and server timezone databases are 100% in
> sync
> (even for those timezones in common)
If we track the server's timezone in the driver, then if we get a
timezone that we don't understand
we can just use the JVM's default time zone.
>
> -O
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 6: explain analyze is your friend
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-07-21 00:46:33 | Re: Timestamp Conversion Woes Redux |
| Previous Message | Oliver Jowett | 2005-07-21 00:20:51 | Re: Timestamp Conversion Woes Redux |