You are viewing a plain text version of this content. The canonical link for it is here.

Posted to derby-dev@db.apache.org by "Bryan Pendleton (JIRA)" <ji...@apache.org> on 2010/01/12 20:32:54 UTC

[jira] Resolved: (DERBY-1562) Have BaseJDBCTestCase have a Connection field to cover the common case where one connection is used.

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

Bryan Pendleton resolved DERBY-1562.
------------------------------------

    Resolution: Fixed
      Assignee: Daniel John Debrunner

I believe that Dan finished all the work described by this sub-task, so marking the issue resolved.

> Have BaseJDBCTestCase have a Connection field to cover the common case where one connection is used.
> ----------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-1562
>                 URL: https://issues.apache.org/jira/browse/DERBY-1562
>             Project: Derby
>          Issue Type: Sub-task
>          Components: Test
>            Reporter: Daniel John Debrunner
>            Assignee: Daniel John Debrunner
>
> Most JDBC tests that extend BaseJDBCTestCase  have their own connection field and their own tearDown method to close the connection, this is all common code that should be in the base class. Once the getConnection method becomes an instance method (rather than a static method see DERBY-1555) then it could create the connection on demand.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.