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] Commented: (DERBY-1234) Verify that we raise SQLException when calling methods on closed java.sql objects
Date Thu, 04 May 2006 12:58:19 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1234?page=comments#action_12377801 ] 

Knut Anders Hatlen commented on DERBY-1234:
-------------------------------------------

Thanks Andreas, you're completely right. I will go back and see if I
can clean things up. The reason for having those extra calls was that
I wanted the is-closed exception to be raised before any other
exceptions (see also Kristian's comment).

> 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: 10.2.0.0
>     Reporter: Rick Hillegas
>     Assignee: Knut Anders Hatlen
>      Fix For: 10.2.0.0
>  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-part5.diff,
derby-1234-part5.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:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message