[DERBY-3436] Embedded closes all open ResultSets on failure in auto-commit mode, whereas client keeps them open

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Duplicate
• Affects Version/s: 10.4.1.3
• Component/s: JDBC
• Urgency: Normal
• Bug behavior facts: Embedded/Client difference
• Assignee: Unassigned
• Reporter: Knut Anders Hatlen
• Created: 20/Feb/08 09:51
• Updated: 18/Aug/10 13:30
• Resolved: 18/Aug/10 13:30

Description

When an error happens in auto-commit mode, the embedded driver will close all open ResultSets (including holdable ones) in that transaction. The client driver will keep the ResultSets open. The embedded driver and the client driver should have the same behaviour.

The test case testAutoCommitFailure() in jdbc4/TestDbMetaData contains code that shows the difference between client and embedded.

DatabaseMetaData.autoCommitFailureClosesAllResultSets() currently returns true on the embedded driver (after DERBY-3422) and false on the client driver to account for this difference.

Issue Links

• duplicates: DERBY-160 Foreign key constraint failure closes the cursors in embedded mode but not in Network Server mode
• is part of: DERBY-310 Document and/or change Derby client code to match behavior with Embedded driver where possible.