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 "Dag H. Wanvik (JIRA)" <ji...@apache.org> on 2011/02/09 02:15:57 UTC

[jira] Commented: (DERBY-5012) [patch] bad allocation guard in ResultSet#resetUpdatedColumnsForInsert

    [ https://issues.apache.org/jira/browse/DERBY-5012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12992266#comment-12992266 ] 

Dag H. Wanvik commented on DERBY-5012:
--------------------------------------

+1 to no-alloc.diff


> [patch] bad allocation guard in ResultSet#resetUpdatedColumnsForInsert
> ----------------------------------------------------------------------
>
>                 Key: DERBY-5012
>                 URL: https://issues.apache.org/jira/browse/DERBY-5012
>             Project: Derby
>          Issue Type: Bug
>          Components: Network Client
>    Affects Versions: 10.7.1.1
>            Reporter: Dave Brosius
>            Priority: Trivial
>             Fix For: 10.8.0.0
>
>         Attachments: bad_allocation_guard.diff, no-alloc.diff
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> code checks to see if an array is _not_ null, and if so allocates the array. This is backwards. Should check to see if the array is null.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira