You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Daniel John Debrunner (JIRA)" <ji...@apache.org> on 2006/11/09 00:56:52 UTC
[jira] Closed: (DERBY-2052) JDBC.assertRowInResultSet compares the
wrong value if using trimmed strings and a SMALLINT column exists.
[ http://issues.apache.org/jira/browse/DERBY-2052?page=all ]
Daniel John Debrunner closed DERBY-2052.
----------------------------------------
Fix Version/s: 10.3.0.0
Resolution: Fixed
> 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
> Assigned To: Daniel John Debrunner
> Fix For: 10.3.0.0
>
> Attachments: derby2052_diff.txt
>
>
> 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