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

Derby

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

Created: 20/Feb/08 09:51 AM Updated: 13/Jul/09 12:00 PM

Return to search

Component/s:

JDBC

Affects Version/s:

10.4.1.3

Fix Version/s:

None

Time Tracking:

Not Specified

Issue Links:

Incorporates

This issue is part of:

~~DERBY-310~~ Document and/or change Derby client code to match behavior with Embedded driver where possible.

Urgency:	Normal
Bug behavior facts:	Embedded/Client difference

Description

« Hide

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.

All

Comments

Work Log

Change History

Subversion Commits

Sort Order:

[ Permlink | « Hide ]

Tiago R. Espinha added a comment - 13/Jul/09 12:00 PM

Triaged for 10.5.2.

Assigned normal urgency.