You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Knut Anders Hatlen (JIRA)" <de...@db.apache.org> on 2006/04/23 15:27:06 UTC
[jira] Commented: (DERBY-1234) Verify that we raise SQLException
when calling methods on closed java.sql objects
[ http://issues.apache.org/jira/browse/DERBY-1234?page=comments#action_12375877 ]
Knut Anders Hatlen commented on DERBY-1234:
-------------------------------------------
Checked in the test in revision 396269. Didn't enable it in any suite since it fails. You can try the test by running
java org.apache.derbyTesting.functionTests.harness.RunTest jdbc4/ClosedObjectTest.junit
and
java -Dframework=DerbyNetClient org.apache.derbyTesting.functionTests.harness.RunTest jdbc4/ClosedObjectTest.junit
> 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-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