[DERBY-3422] Embedded returns wrong value for DatabaseMetaData.autoCommitFailureClosesAllResultSets()

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 10.4.1.3
• Fix Version/s: 10.3.3.0, 10.4.1.3
• Component/s: JDBC
• Assignee: Knut Anders Hatlen
• Reporter: Knut Anders Hatlen
• Created: 15/Feb/08 14:41
• Updated: 18/Aug/10 13:30
• Resolved: 20/Feb/08 09:36

Description

DatabaseMetaData.autoCommitFailureClosesAllResultSets() returns false both on the client and on embedded. However, the embedded driver does in fact close all open result sets when an error occurs in auto-commit mode. There is a test case in jdbc4.TestDbMetaData to test this (testAutoCommitFailure), but it only uses ResultSet.isClosed() to check whether or not the result set is closed after the failure. Because of DERBY-3404, isClosed() returns false for the result sets that have been closed because of the failure, so the test doesn't reveal the bug. If the test is changed to invoke methods on the result set (e.g. next()) instead of calling isClosed(), we'll see that the result set is in fact closed and get an SQLException with SQL state XCL16.

Issue Links

• is related to: DERBY-160 Foreign key constraint failure closes the cursors in embedded mode but not in Network Server mode