db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-1234) Verify that we raise SQLException when calling methods on closed java.sql objects
Date Wed, 03 May 2006 08:01:48 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1234?page=all ]

Knut Anders Hatlen updated DERBY-1234:

    Attachment: derby-1234-part4.diff

New patch (part4) which fixes the issues in EmbedConnection:

  1) New method checkIfClosed() which throws exception when the
     connection is closed.

  2) Added getTypeMap() with generic signature to avoid compiler

  3) Modified jdbc4/ClosedObjectTest.junit so that it doesn't expect
     isValid() to throw exception when the connection is closed.

  4) Added a test case for getTypeMap() to
     jdbc4/ConnectionTest.junit. It turned out this test case fails on
     BrokeredConnection. Will fix that in a later patch. (The test is
     not enabled in any suite, since there are other test cases
     failing on BrokeredConnection as well.)

Derbyall and jdbc40 ran cleanly. Please review.

> Verify that we raise SQLException when calling methods on closed java.sql objects
> ---------------------------------------------------------------------------------
>          Key: DERBY-1234
>          URL: http://issues.apache.org/jira/browse/DERBY-1234
>      Project: Derby
>         Type: Improvement

>   Components: JDBC
>     Versions:
>     Reporter: Rick Hillegas
>     Assignee: Knut Anders Hatlen
>      Fix For:
>  Attachments: derby-1234-part1.diff, derby-1234-part2.diff, derby-1234-part2.stat, derby-1234-part3.diff,
derby-1234-part3.stat, derby-1234-part4.diff, derby-1234-part4.stat, derby-1234-v1.diff, derby-1234-v1.stat
> The next rev of the JDBC4 spec will clarify that databases should raise SQLException
when an application calls methods on closed sql objects: ResultSet, Preparedstatement, CallableStatement,
Connection, and Statement. We should verify that we conform.

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