[ http://issues.apache.org/jira/browse/DERBY-1234?page=comments#action_12377739 ]
Dyre Tjeldvoll commented on DERBY-1234: --------------------------------------- I have looked at the part4 patch (a2ps --prologue=diff -Eudiff, is awesome :), and I think it looks good. I must say the the workaround to avoid the compiler warning is somewhat of a hack. A clever hack, but still a hack... :) But I have seen the discussion and agree that it is the lesser evil. +1 to commit. > 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-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
