Re: Timestamp Conversion Woes Redux

From: Dave Cramer <pg(at)fastcrypt(dot)com>
To: Oliver Jowett <oliver(at)opencloud(dot)com>
Cc: pgsql-jdbc(at)postgresql(dot)org
Subject: Re: Timestamp Conversion Woes Redux
Date: 2005-07-19 13:18:35
Message-ID: 499DFF86-4F92-47D1-A9FE-F9EEEB0E8BAF@fastcrypt.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

Oliver,

setString is "special" because historically this is what we see in
the upgrade problems. People try to insert a date using setString
('dateval') etc.

Also we have historically told people to use setString to insert pg
specific types, when there was no corresponding java type.

I am not suggesting that we type all parameters as UNKNOWN only
String parameters.

Dave
On 19-Jul-05, at 9:07 AM, Oliver Jowett wrote:

> Dave Cramer wrote:
>
>
>> by typing it as UNKNOWN we are letting the backend decide what to
>> do with it. There is considerable code in there to do the "right"
>> thing.
>>
>
> So you are suggesting we type all parameters as UNKNOWN regardless
> of which setXXX() accessor was used to set them?
>
> If not, why is setString() special?
>
> -O
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 5: don't forget to increase your free space map settings
>
>

In response to

Responses

Browse pgsql-jdbc by date

  From Date Subject
Next Message Oliver Jowett 2005-07-19 13:22:11 Re: Timestamp Conversion Woes Redux
Previous Message Oliver Jowett 2005-07-19 13:07:17 Re: Timestamp Conversion Woes Redux