Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Sat, 16 Apr 2011 03:42:05 +0000 (UTC)
From: "Dave Brosius (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: 
 <872253264.62025.1302925325864.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 ]

Dave Brosius updated DERBY-5163:
--------------------------------

    Attachment: sql_cleanup_fixes.diff

Cleanup patch so that we don't close statements when resultsets from those statements are still active.

> [patch] fix up sql cleanup handling
> -----------------------------------
>
>                 Key: DERBY-5163
>                 URL: https://issues.apache.org/jira/browse/DERBY-5163
>             Project: Derby
>          Issue Type: Improvement
>          Components: Tools
>    Affects Versions: 10.7.1.1
>            Reporter: Dave Brosius
>            Priority: Trivial
>             Fix For: 10.8.1.1
>
>         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