db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel John Debrunner (JIRA)" <j...@apache.org>
Subject [jira] Created: (DERBY-2052) JDBC.assertRowInResultSet compares the wrong value if using trimmed strings and a SMALLINT column exists.
Date Wed, 08 Nov 2006 00:48:56 GMT
JDBC.assertRowInResultSet compares the wrong value if using trimmed strings and a SMALLINT
column exists.
---------------------------------------------------------------------------------------------------------

                 Key: DERBY-2052
                 URL: http://issues.apache.org/jira/browse/DERBY-2052
             Project: Derby
          Issue Type: Bug
          Components: Test
    Affects Versions: 10.3.0.0
            Reporter: Daniel John Debrunner


There is a bug in assertRowInResultSet where a path through the loop does not set the variable
obj.
This leads to it being compared with the previous value.

Using locally scoped variables within the loop would have most likely caught this bug at development
time.
Then the compiler sees that obj has one uninitialzed path through the code and throws an error.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message