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

From Dave Cramer
Subject Re: Timestamp Conversion Woes Redux
Date
Msg-id C36F2D5F-093E-489C-8D6F-A67B746EA6C8@fastcrypt.com
Whole thread Raw
In response to Re: Timestamp Conversion Woes Redux  (Oliver Jowett <oliver@opencloud.com>)
Responses Re: Timestamp Conversion Woes Redux
List pgsql-jdbc
I'm also thinking we should use UNKOWN for setString as well,
hopefully this would reduce the number of upgrade problems people are
having when they upgrade from 7.x to 8.x

Dave
On 18-Jul-05, at 7:13 PM, Oliver Jowett wrote:

> Dave Cramer wrote:
>
>
>> You are correct, the driver is binding it to a timestamptz. The
>> underlying data is without
>> timezone so the server probably attempts to remove it
>>
>> I'm starting to think that binding the type to "unknown" might be
>> better as you suggested earlier.
>>
>
> Yeah, given that we can't work out which of the two types is intended
> ahead of time, this might be the best idea..
>
> Christian, you should be able to test this easily enough by modifying
> setTimestamp() to pass Oid.UNKNOWN instead of Oid.TIMESTAMPTZ to
> bindString().
>
> -O
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster
>
>


pgsql-jdbc by date:

Previous
From: Oliver Jowett
Date:
Subject: Re: org.postgresql.util.PSQLException: ERROR: current transaction
Next
From: Oliver Jowett
Date:
Subject: Re: Timestamp Conversion Woes Redux