commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matt Jiang (JIRA)" <j...@apache.org>
Subject [jira] Created: (DBUTILS-42) Object with Long or Decimal got initial zero value while database field is null
Date Tue, 16 Oct 2007 13:15:50 GMT
Object with Long or Decimal got initial zero value while database field is null
-------------------------------------------------------------------------------

                 Key: DBUTILS-42
                 URL: https://issues.apache.org/jira/browse/DBUTILS-42
             Project: Commons DbUtils
          Issue Type: Improvement
    Affects Versions: 1.1
         Environment: JDK 5.0, MSSQL 2000
            Reporter: Matt Jiang


While I use dbutil1.1, I got a big different implementation betweeb 1.0 and 1.1.
Given a Java object, it has a property with Long data type; mapping to database, its table
field datatype is bigint.
If it has a record and its value is null.

In 1.0 implementation, if I load entity, then we can see the property in Java object is also
null.
But in 1.1 implementation, the Java object will got a Long object with 0 inside.

This behavior change does big impact if I upgrade from 1.0 to 1.1. It might make application
logic fail because origional null status now become a Long(0) value to map to null value in
database.

I suggest to change it back. If null value in database, then mapped Java object should be
null as well, not new a Long(0) to be a initial value.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message