Re: TypeInfoCache

From: Oliver Jowett <oliver(at)opencloud(dot)com>
To: dmp <danap(at)ttc-cmc(dot)net>
Cc: pgsql-jdbc(at)postgresql(dot)org
Subject: Re: TypeInfoCache
Date: 2007-12-22 21:28:41
Message-ID: 476D8189.4030003@opencloud.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

dmp wrote:

> I would rather not have to CAST or import non-standard types which are not
> defined in the Sun JDBC. If you wish to have them at least make the driver
> except a generic string setter method like the getter.

You can now do this in CVS HEAD by using setObject(n, someStringObject,
Types.OTHER). Or you can enable it globally for all strings by using
"stringtype=unspecified" at the cost of less type safety (which I
wouldn't recommend)

Normally the meaning of setString() is pretty explicit, though - it says
that you want the target type to be text or varchar. If the underlying
database type is something different, I don't think it's unreasonable to
require you to either use a different method, or put a cast in your query.

-O

In response to

Browse pgsql-jdbc by date

  From Date Subject
Next Message Christian Schröder 2007-12-23 23:15:44 Re: Missing fields in getColumns() result
Previous Message dmp 2007-12-22 21:04:28 Re: TypeInfoCache