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:04:31
Message-ID: F84A33B1-609F-4E31-835D-C89E3372B349@fastcrypt.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

Oliver,

Sorry for bringing this up again. I realize we have discussed this
before.

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.

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

> Dave Cramer wrote:
>
>> Can you explain your rationale ?
>>
>
> I don't really want to rehash this again and again, but it boils
> down to: if setString() does not type the parameter as a string,
> how *do* I type a parameter as a string?
>
> I do not find "there are lots of broken applications out there" a
> particularly convincing argument for changing this.
>
> -O
>
>

In response to

Responses

Browse pgsql-jdbc by date

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