db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-1234) Verify that we raise SQLException when calling methods on closed java.sql objects
Date Fri, 28 Apr 2006 19:45:39 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1234?page=comments#action_12376984 ] 

Rick Hillegas commented on DERBY-1234:

Looks good to me. Ready for commit. For extra credit, we could add a test, modelled on VerifySignatures
or UnsupportedVetter, which calls all methods on closed objects and verifies that they either
raise the ObjectClosed exception or SQLFeatureNotSupportedException.

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