db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] Created: (DERBY-3436) Embedded closes all open ResultSets on failure in auto-commit mode, whereas client keeps them open
Date Wed, 20 Feb 2008 09:52:43 GMT
Embedded closes all open ResultSets on failure in auto-commit mode, whereas client keeps them
open
--------------------------------------------------------------------------------------------------

                 Key: DERBY-3436
                 URL: https://issues.apache.org/jira/browse/DERBY-3436
             Project: Derby
          Issue Type: Bug
          Components: JDBC
    Affects Versions: 10.4.0.0
            Reporter: Knut Anders Hatlen
            Priority: Minor


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.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message