[DERBY-4890] Different string to boolean conversion on embedded and client

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.7.1.1
• Fix Version/s: 10.7.1.1
• Component/s: JDBC
• Issue & fix info: Repro attached
• Bug behavior facts: Embedded/Client difference
• Assignee: Richard N. Hillegas
• Reporter: Knut Anders Hatlen
• Created: 06/Nov/10 01:44
• Updated: 29/Nov/10 14:21
• Resolved: 08/Nov/10 23:04

Description

The following code fragment behaves differently on client and embedded:

PreparedStatement ps = c.prepareStatement("values cast(? as boolean)");
ps.setString(1, "TRUE");
ResultSet rs = ps.executeQuery();
rs.next();
System.out.println(rs.getBoolean(1));

Embedded prints "true". Client raises an exception:

Exception in thread "main" java.sql.SQLDataException: An attempt was made to get a data value of type 'VARCHAR' from a data value of type 'BOOLEAN'.
at org.apache.derby.client.am.SQLExceptionFactory40.getSQLException(SQLExceptionFactory40.java:72)
at org.apache.derby.client.am.SqlException.getSQLException(SqlException.java:358)
at org.apache.derby.client.am.PreparedStatement.setString(PreparedStatement.java:884)
at SetByte.main(SetByte.java:6)
Caused by: org.apache.derby.client.am.SqlException: An attempt was made to get a data value of type 'VARCHAR' from a data value of type 'BOOLEAN'.
at org.apache.derby.client.am.PreparedStatement$PossibleTypes.throw22005Exception(PreparedStatement.java:3069)
at org.apache.derby.client.am.PreparedStatement.setString(PreparedStatement.java:874)
... 1 more

Issue Links

• relates to: DERBY-4891 Enable testing of boolean type in ParameterMappingTest