[DERBY-5788] BIT support regression and confusing message in 10.8.2.2: org.apache.derby.client.am.SqlException: Invalid character string format for type BOOLEAN

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 10.8.2.2
• Component/s: JDBC
• Labels: derby_triage10_10
• Environment: Windows 7 (All)
• Urgency: Normal
• Assignee: Unassigned
• Reporter: Radoslav Ivanov
• Created: 28/May/12 13:30
• Updated: 25/Sep/12 18:23

Description

Scenario (on 10.8.2.2; with 10.5.1.1 the problem does not appear): when setting BIT from this example :

rsSch.createTab("Bit_Tab",sqlp,conn);
String sMaxBooleanVal = rsSch.extractVal("Bit_Tab",1,sqlp,conn); //value is “1“
cstmt = conn.prepareCall("

{call Bit_In_Min(?)}

");

cstmt.setObject(1,sMaxBooleanVal,java.sql.Types.BIT); //-> throws the exception below

Exception (Problem with not supporting “0” and “1” for the type BIT; moreover, confusing message):
java.sql.SQLDataException: Invalid character string format for type BOOLEAN.
at org.apache.derby.client.am.SQLExceptionFactory40.getSQLException(Unknown Source)
at org.apache.derby.client.am.SqlException.getSQLException(Unknown Source)
at org.apache.derby.client.am.PreparedStatement.setObject(Unknown Source)
at org.apache.commons.dbcp.DelegatingPreparedStatement.setObject(DelegatingPreparedStatement.java:166)
at org.apache.commons.dbcp.DelegatingPreparedStatement.setObject(DelegatingPreparedStatement.java:166)
at com.sun.ts.tests.jdbc.ee.callStmt.callStmt10.callStmtClient10.testSetObject48(callStmtClient10.java:812)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

Issue Links

• relates to: DERBY-4964 Client driver fails to convert string to boolean with setObject(col, str, Types.BIT)
• relates to: DERBY-4965 Boolean to char conversion results in integer