[DERBY-1863] SQL NULL always represented as zero when mapping an INTEGER column to a Java int or Integer field using a EOD query object extended from BaseQuery

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 10.2.1.6, 10.3.1.4
• Component/s: JDBC
• Environment: Mustang b98
• Assignee: Unassigned
• Reporter: Daniel John Debrunner
• Created: 18/Sep/06 20:55
• Updated: 06/Oct/06 17:43
• Resolved: 06/Oct/06 17:43

Description

SQL INTEGER column mapped to a Java primitive int field resulted in the filed set to zero when the SQL value was NULL.
This means there is no way to tell if the field was NULL or not. I was expecting some error, either at "mapping" time or at exection time.

SQL INTEGER column mapped to a Java java.lang.Integer field resulted in the filed set to zero when the SQL value was NULL.
Was expecting the field to be set to Java null. Note for VARCHAR columns mapped to a String field, the result is Java null when the SQL value is NULL.

JDBC 4.0 spec seems silent on the expected behaviour for @Select queries and the column mapping when the SQL value is NULL.