db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bryan Pendleton (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-1562) Have BaseJDBCTestCase have a Connection field to cover the common case where one connection is used.
Date Mon, 07 Dec 2009 04:50:18 GMT

    [ https://issues.apache.org/jira/browse/DERBY-1562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12786778#action_12786778
] 

Bryan Pendleton commented on DERBY-1562:
----------------------------------------

Perhaps I'm misunderstanding the description, but I think that 
Dan actually finished all of this work as part of the following changes:

https://svn.apache.org/viewvc?view=revision&revision=431999
https://svn.apache.org/viewvc?view=revision&revision=432222
https://svn.apache.org/viewvc?view=revision&revision=432328

I believe we can mark this sub-task as complete.

> 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
>
> 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.


Mime
View raw message