db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (DERBY-5285) [patch] avoid npe if tempCongloms is null
Date Fri, 25 May 2012 10:51:23 GMT

     [ https://issues.apache.org/jira/browse/DERBY-5285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Knut Anders Hatlen resolved DERBY-5285.
---------------------------------------

          Resolution: Duplicate
       Fix Version/s:     (was: 10.8.2.2)
                      10.10.0.0
    Issue & fix info:   (was: Patch Available)

Marking the issue as resolved, as DERBY-3371 has been fixed.
                
> [patch] avoid npe if tempCongloms is null
> -----------------------------------------
>
>                 Key: DERBY-5285
>                 URL: https://issues.apache.org/jira/browse/DERBY-5285
>             Project: Derby
>          Issue Type: Improvement
>          Components: Store
>    Affects Versions: 10.8.2.2
>            Reporter: Dave Brosius
>            Assignee: Mike Matrigali
>            Priority: Trivial
>             Fix For: 10.10.0.0
>
>         Attachments: npe_guard.diff
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> if (tempCongloms != null)
> 	tempCongloms.remove(new Long(conglomId));
> tempCongloms.put(new Long(conglomId), conglom);
> code guards against tempCongloms being null for the remove, but not for the put. so put
the put in the if statement.
> Then realized that the remove is superfluous, as the put will overright so just removed
the remove.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message