null values for columns mapped as "boolean" cause exception when saving entity with Sybase jdbc4

Description

ASE doesn't allow 'null' value for 'BIT' datatype;
While performing insert operation using jconn3.jar it permit you to have
'null' value, this 'null' value is converted into bit 0 by jconn3 & hence
ASE doesn't throw any exception;
But incase of jconn4.jar 'null' value is not converted into bit 0, hence
jconn4 directly reports an exception for 'null' value(which is the expected
correct behavior)

Hibernate persists a null Boolean value by calling:

PreparedStatement.setNull( index, java.sql.Types.BIT )

The SQL code, java.sql.Types.BIT, is used because the Hibernate BooleanType defines its code as java.sql.Type.BIT.

This can be reproduced using an annotations unit test, Java5FeaturesTest.testAutoboxing()..

Sybase maps bit columns to tinyint, so when the unit test is executed, the column in the underlying table is actually of type tinyint, not bit. Sybase allows nullable tinyint columns, so there should be no problem persisting a null value as null.

I've verified that changing the call to:
PreparedStatement.setNull( index, java.sql.Types.TINYINT )
persists the null value without being converted to 0.

Environment

Sybase jdbc4

Status

Assignee

Strong Liu

Reporter

Strong Liu

Fix versions

Labels

None

backPortable

None

Suitable for new contributors

None

Requires Release Note

None

Pull Request

None

backportDecision

None

Components

Affects versions

3.5.3
3.5.4
3.6.0.Beta1

Priority

Major
Configure