db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dag H. Wanvik (JIRA)" <j...@apache.org>
Subject [jira] Created: (DERBY-3115) With embedded driver and autocommit, when closing a connection, updates on updatable result set are lost, unless result set is closed
Date Mon, 08 Oct 2007 12:10:50 GMT
With embedded driver and autocommit, when closing a connection, updates on updatable result
set are lost, unless result set is closed
-------------------------------------------------------------------------------------------------------------------------------------

                 Key: DERBY-3115
                 URL: https://issues.apache.org/jira/browse/DERBY-3115
             Project: Derby
          Issue Type: Bug
          Components: JDBC
    Affects Versions: 10.3.1.4
            Reporter: Dag H. Wanvik


With autocommit, if an application neglects to close the result set
and/or the statement, the closing of the connection will lose any
updates performed via an updatable result set.

If autocommit is false, SQL state 25000 invalid transaction state will
be thrown, however.

The JDBC standard requires that statements be closed when the
connection is closed, cf.  JDBC 4, section 9.4.4: "All Statement
objects created from a given Connection object will be closed when the
close method for the object is called."  For updatable result sets,
closing the statement would lead to a closing of the result set, and
hence a commit of the updates.

For the network client it works as expected.


-- 
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