Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Wed, 17 Aug 2011 20:27:27 +0000 (UTC)
From: "Kathey Marsden (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: 
 <761283210.46489.1313612847225.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1355285592.20630.1301461085740.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (DERBY-5163) [patch] fix up sql cleanup handling
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ 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: 10.7.1.1
>            Reporter: Dave Brosius
>            Assignee: Dave Brosius
>            Priority: Trivial
>             Fix For: 10.9.0.0
>
>         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