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

From Dave Cramer
Subject Re: Timestamp Conversion Woes Redux
Date
Msg-id A3338300-ABD6-474D-AC3D-84A4E4546BE1@fastcrypt.com
Whole thread Raw
In response to Re: Timestamp Conversion Woes Redux  (Csaba Nagy <nagy@ecircle-ag.com>)
Responses Re: Timestamp Conversion Woes Redux  (Csaba Nagy <nagy@ecircle-ag.com>)
Re: Timestamp Conversion Woes Redux  (Oliver Jowett <oliver@opencloud.com>)
List pgsql-jdbc
For that matter we could use a PGUnknown type as well.

Dave.
On 19-Jul-05, at 10:52 AM, Csaba Nagy wrote:

> [snip]
>
>> wasn't the whole thread.  I agree with you that if we make setString
>> default to UNKNOWN, there had better be a way to say "by golly this
>> really is TEXT" for the corner cases.  It'd be a good idea if it
>> wasn't
>> limited to TEXT, either, but could allow specification of any random
>> datatype.
>>
>
> This makes me think, isn't it possible to introduce a special type to
> say something like: setObject(..., Types.UNKNOWN), and map that to
> setting a string with type unknown ? In that case people could
> still use
> prepared statements with parameters of unknown type, it just have
> to be
> explicit. For me that would have been a much simpler "fixing the app".
>
> Cheers,
> Csaba.
>
>
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 4: Have you searched our list archives?
>
>                http://archives.postgresql.org
>
>


pgsql-jdbc by date:

Previous
From: Dave Cramer
Date:
Subject: Re: Timestamp Conversion Woes Redux
Next
From: Csaba Nagy
Date:
Subject: Re: Timestamp Conversion Woes Redux