Is this true. If so, is there anytime schedule for a fix?
Thanks, Ian
Dan,
I really think there is something wrong with the boolean (bit) type setting
within the PostgreSQL JDBC driver. After checking w/ news groups and
receiving one answer below, I think the only way I can accomplish what I
need to is to go to postresql itself. Do you have any ideas?
Hi Joe,
I appreciate your response. I put in a workaround if I'm dealing with
postgresql like the following:
if (value instanceof Boolean &&
getType().equals(PersistentStore.PostgreSQL)) {
Trace.println("Setting Boolean value for "+objAttr.getName()+"="+value);
preparedStatement.setBoolean(i, ((Boolean)value).booleanValue()); }
else {
preparedStatement.setObject(i, value); }
and saw the output:
..
SQL: insert into Car (License,Color,Logo,Sunroof) values (?,?,?,?)
Setting Boolean value for Sunroof=false
..
with exactly the same problem, so calling setBoolean didn't work either. Do
you have any suggestions on how to get in touch with the appropriate
PostgreSQL people?
Thanks, Ian
-----Original Message-----
From: Joe Weinstein [mailto:joe@bea.com]
Sent: Monday, January 08, 2001 5:31 PM
To: Ian deSouza
Subject: Re: org.postgresql.Driver Problem?
Ian deSouza wrote:
Sorry, the value was equals to true when I get zpbit_in: t is not a valid
bitstring and when value
is false I get
zpbit_in: f is not a valid bitstring .
Hi Ian.
You shouldn't use setObject() unless you are sending
the driver a Driver-understandable java.sql Object.
In this case, you should probably just use setBoolean().
