Skip site navigation (1) Skip section navigation (2)

Re: BUG #3751: Conversion error using PreparedStatement.setObject()

From: Kris Jurka <books(at)ejurka(dot)com>
To: "Lance J(dot) Andersen" <Lance(dot)Andersen(at)Sun(dot)COM>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #3751: Conversion error using PreparedStatement.setObject()
Date: 2007-11-16 01:02:13
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-bugs
Lance J. Andersen wrote:
> Thank you for your time, but i think there is still a driver issue here:
> If i use the same  types as i sent in the email and execute
> select * from  bit_in_min(1::bit)
> I have no problems and the table is correctly updated.
> This would lead me to believe that the driver has a problem with 
> correctly mapping the setObect() of the String to a BIT which is 
> required conversion by the JDBC spec.

According to our reading of the JDBC spec java.sql.Types.BIT and BOOLEAN 
are equivalent.  So it doesn't make sense to map BIT to one server type 
and BOOLEAN to another.  When thinking about Types.BIT it's easy to see 
a server type named "bit" and assume it's a match, but for the semantics 
of Types.BIT, we think boolean is a better match.

Just because "bit" can be made to work doesn't make it the best option. 
  Particularly our concern arises from what to do when returning meta 
data.  Consider a table that has columns "a bit(1), b bit(2)".  While a 
does have boolean semantics because it's limited to a length of 1, b is 
not.  Returning b as Types.BIT would be a mistake.  Driving this 
decision solely on the length attribute is not good because the server 
will not give you the length information in certain circumstances and 
all you'll have is the raw "bit" type name.  This is why we've chose to 
use boolean as the server type for Types.BIT + BOOLEAN.

Kris Jurka

In response to


pgsql-bugs by date

Next:From: RaviKumar.kapaDate: 2007-11-16 05:13:21
Subject: BUG #3754: postgresql+hibernate
Previous:From: Lance J. AndersenDate: 2007-11-16 00:28:38
Subject: Re: BUG #3751: Conversion error using PreparedStatement.setObject()

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group