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

From Dave Cramer
Subject Re: Timestamp Conversion Woes Redux
Date
Msg-id E14D759B-135D-4531-9322-9F4C535C2627@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
Oliver,

Can you explain your rationale ?

Mine is:

The overhead isn't that bad.
Anyone using the API correctly will not be affected ( assuming they
use setInt() etal correctly )

Philosophically speaking, making the driver more strict does not make
it easier for people to convert to postgresql. AFAICT, most drivers
tend to be more lenient.

Dave

On 19-Jul-05, at 8:23 AM, Oliver Jowett wrote:

> Dave Cramer wrote:
>
>> 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
>>
>
> I still think this is a bad idea.
>
> -O
>
>


pgsql-jdbc by date:

Previous
From: Oliver Jowett
Date:
Subject: Re: Timestamp Conversion Woes Redux
Next
From: Oliver Jowett
Date:
Subject: Re: Timestamp Conversion Woes Redux