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] [Updated] (DERBY-5711) NullsTest doesn't call super.tearDown()
Date Tue, 24 Apr 2012 13:01:34 GMT

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

Knut Anders Hatlen updated DERBY-5711:

    Attachment: d5711-1a.diff

Since the current tearDown() method only calls setAutoCommit(), which is not neccessary since
the connection is not going to be used anymore, I've removed the method in the attached patch.
Then NullsTest will inherit BaseJDBCTestCase.tearDown() and do the right thing automatically.
> NullsTest doesn't call super.tearDown()
> ---------------------------------------
>                 Key: DERBY-5711
>                 URL: https://issues.apache.org/jira/browse/DERBY-5711
>             Project: Derby
>          Issue Type: Bug
>          Components: Test
>    Affects Versions:
>            Reporter: Knut Anders Hatlen
>            Assignee: Knut Anders Hatlen
>         Attachments: d5711-1a.diff
> NullsTest has the following tearDown() method:
>     public void tearDown() throws SQLException{
>         getConnection().setAutoCommit(true);
>     }
> Since it doesn't call super.tearDown(), it doesn't release connections and statements.

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


View raw message