Thread: f is not a valid bitstring

I have an entity bean that uses a boolean for a field, and that boolean maps to a bit field in the database.  Is this the proper field I should be mapping to?  Under Sybase and MSSQL 7, there were no problems with sending "true" or "false" through the bean - something took care of it and mapped it properly.  Under Postgres 7.0.3, however, I consistently get this error:

java.sql.SQLException: ERROR:  zpbit_in: f is not a valid bitstring

I've traced it back, and found that it's taking the first letter of the boolean value and trying to put that into the bit field instead of changing it to a 1 or 0.  Any suggestions?

Thanks a bunch...

Walt Skidmore

An update: I looked through the documentation, and found that the bool type might be better suited.  So, after changing the field type, I'm getting a new error:

java.sql.SQLException: ERROR: pg_atoi: error in "f": can't parse "f"

Any ideas?

Thanks...

 -----Original Message-----
From:   Skidmore, Walt 
Sent:   Friday, February 23, 2001 9:00 AM
To:     'pgsql-jdbc@postgresql.org'
Subject:        f is not a valid bitstring

I have an entity bean that uses a boolean for a field, and that boolean maps to a bit field in the database.  Is this the proper field I should be mapping to?  Under Sybase and MSSQL 7, there were no problems with sending "true" or "false" through the bean - something took care of it and mapped it properly.  Under Postgres 7.0.3, however, I consistently get this error:

java.sql.SQLException: ERROR:  zpbit_in: f is not a valid bitstring

I've traced it back, and found that it's taking the first letter of the boolean value and trying to put that into the bit field instead of changing it to a 1 or 0.  Any suggestions?

Thanks a bunch...

Walt Skidmore

At 09:00 23/02/01 -0800, Skidmore, Walt wrote:

>I have an entity bean that uses a boolean for a field, and that boolean
>maps to a bit field in the database.  Is this the proper field I should be
>mapping to?  Under Sybase and MSSQL 7, there were no problems with sending
>"true" or "false" through the bean - something took care of it and mapped
>it properly.  Under Postgres 7.0.3, however, I consistently get this error:
>
>java.sql.SQLException: ERROR:  zpbit_in: f is not a valid bitstring
>
>I've traced it back, and found that it's taking the first letter of the
>boolean value and trying to put that into the bit field instead of
>changing it to a 1 or 0.  Any suggestions?


Ok, first what version are you using. Second what methods are you (or the
bean container) using to set it.

Peter


>Thanks a bunch...
>
>Walt Skidmore

At 15:17 23/02/01 -0800, Skidmore, Walt wrote:

>An update: I looked through the documentation, and found that the bool
>type might be better suited.  So, after changing the field type, I'm
>getting a new error:
>
>java.sql.SQLException: ERROR: pg_atoi: error in "f": can't parse "f"

Hmm, its trying to use a numeric method to access the book. Can you give me
the _Full_ stacktrace for this?

Peter


>Any ideas?
>
>Thanks...
>
>  -----Original Message-----
>From:   Skidmore, Walt
>Sent:   Friday, February 23, 2001 9:00 AM
>To:     'pgsql-jdbc@postgresql.org'
>Subject:        f is not a valid bitstring
>
>I have an entity bean that uses a boolean for a field, and that boolean
>maps to a bit field in the database.  Is this the proper field I should be
>mapping to?  Under Sybase and MSSQL 7, there were no problems with sending
>"true" or "false" through the bean - something took care of it and mapped
>it properly.  Under Postgres 7.0.3, however, I consistently get this error:
>
>java.sql.SQLException: ERROR:  zpbit_in: f is not a valid bitstring
>
>I've traced it back, and found that it's taking the first letter of the
>boolean value and trying to put that into the bit field instead of
>changing it to a 1 or 0.  Any suggestions?
>
>Thanks a bunch...
>
>Walt Skidmore