db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Van Couvering (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-1097) Add tests for Statement.isClosed()
Date Wed, 22 Mar 2006 00:40:10 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1097?page=comments#action_12371364 ] 

David Van Couvering commented on DERBY-1097:

Hi, Kristian.  Sorry to bounce this back, but Rick's latest jdbc40 test suite checkin has
thrown a spanner in the works.

I am a little unclear how Rick's checkin impacts your patch here.  Can you investigate and
make any necessary/useful changes?  It looks like some of your workaround may be avoided now?

Rick, could you look at this patch and suggest how things might have changed with your rework
of the jdbc40 tests?



> Add tests for Statement.isClosed()
> ----------------------------------
>          Key: DERBY-1097
>          URL: http://issues.apache.org/jira/browse/DERBY-1097
>      Project: Derby
>         Type: Sub-task
>   Components: Test
>     Versions:
>  Environment: JDBC4 / JDK 1.6
>     Reporter: Kristian Waagan
>     Assignee: Kristian Waagan
>  Attachments: DERBY-1097-2a.diff, DERBY-1097-2a.stat, DERBY-1097-2b.diff, StatementTest.java,
StatementTest.java-v1, StatementTestSetup.java, StatementTestSetup.java-v1
> Add tests for Statement.isClosed() (implemented as part of DERBY-953).
> The tests are already written, but because of some "confusion" and diverging paths regarding
how to get connections when running JUnit tests, they are held back.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message