[ http://issues.apache.org/jira/browse/DERBY-611?page=comments#action_12357978 ]
Dag H. Wanvik commented on DERBY-611: ------------------------------------- deleteRow has the same problem. In both cases (updateRow and deleteRow), there is explicit code to make a commit happen is autocommit is on. > Network client: updateRow() causes a commit when autoCommit = true > ------------------------------------------------------------------ > > Key: DERBY-611 > URL: http://issues.apache.org/jira/browse/DERBY-611 > Project: Derby > Type: Bug > Components: Network Client > Environment: Java Version: 1.5.0_01 > Java Vendor: Sun Microsystems Inc. > Java home: /usr/jdk/instances/jdk1.5.0/jre > Java classpath: classes > OS name: SunOS > OS architecture: x86 > OS version: 5.10 > Reporter: Fernanda Pizzorno > Priority: Minor > Attachments: testCSUpdateRowCommits.java > > On the network client driver, the ResultSet method updateRow makes the > transaction commit, when autocommit is true. The correct behavior is to > commit only when the result set is closed. This works correctly in the > embedded driver. > The repro case is uploaded as an attachment "testCSUpdateRowCommits.java". > Output (repro case): > updateRow() should not commit > Value: 16, expected value 1. Should not have committed updateRow() -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
