db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (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:42:18 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1234?page=comments#action_12377796 ] 

Kristian Waagan commented on DERBY-1234:
----------------------------------------

Although not directly related to this issue, I would like to comment that some care should
be taken to ensure exceptions are thrown in the "same order" in the different methods and
on the embedded and client side.

For instance, when writing a JUnit test for another issue, I found that Derby threw a "not
an OUT/INOUT" parameter on the client side and a data conversion error exception on the embedded
side (for the same call/test code). Depending on the implementation, moving a condition check
up or down the callstack can change which error condition is encountered first.

> 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