db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-5163) [patch] fix up sql cleanup handling
Date Wed, 17 Aug 2011 20:27:27 GMT

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

Kathey Marsden updated DERBY-5163:

    Issue Type: Bug  (was: Improvement)

Changing this to a bug.  Looking at the change,  I wonder if it is ok to completely throw
away the errors closing statements. It would be nice to see those included with a setNextException()
so all errors get reported.

> [patch] fix up sql cleanup handling
> -----------------------------------
>                 Key: DERBY-5163
>                 URL: https://issues.apache.org/jira/browse/DERBY-5163
>             Project: Derby
>          Issue Type: Bug
>          Components: Tools
>    Affects Versions:
>            Reporter: Dave Brosius
>            Assignee: Dave Brosius
>            Priority: Trivial
>             Fix For:
>         Attachments: sql_cleanup_fixes.diff
> When a sql exception occurs, don't allow potential cascading sql problems when closing
sql objects from masking the original cause of the exception.
> Also make sure statements get closed.

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


View raw message