Resolution: Won't Fix
Affects Version/s: 10.2.1.6, 10.3.1.4
Fix Version/s: None
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.
|Transition||Time In Source Status||Execution Times||Last Executer||Last Execution Date|
|17d 20h 47m||1||Daniel John Debrunner||06/Oct/06 17:43|
|Workflow||jira [ 12383966 ]||Default workflow, editable Closed status [ 12798150 ]|
|Status||Open [ 1 ]||Closed [ 6 ]|
|Resolution||Won't Fix [ 2 ]|
|Field||Original Value||New Value|