db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dag H. Wanvik (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-611) Network client: updateRow() causes a commit when autoCommit = true
Date Tue, 13 Dec 2005 01:10:48 GMT
     [ http://issues.apache.org/jira/browse/DERBY-611?page=all ]

Dag H. Wanvik updated DERBY-611:

    Attachment: 611.stat

I have uploaded a fix for this problem (611.{stat,diff}), and added a
new test (look for "Positive Test34") to lang/updatableResultSet.java.
The network client driver canons are also changed in the case of three
error messages due to the changed behavior, in addition to the change
due to new test.

The patch removes the explicit (auto)commit code in the network client
driver in deleteRow and updateRow, making it behave as the embedded
driver in this respect (modulo error messages).

I have run lang/updatableResultSet.java successfully with Sun jdk 1.3,
1.4 and 1.5 (the two latter has another canon) on Solaris
10/x86. Also, there is a separate canon under j9_13 for this test,
which I have updated, but not been able to test.

I have also run derbyall successfully with jdk 1.4, also on Solaris
10/x86, albeit with some errors in unrelated tests (lang/dcl,

> 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
>     Versions:,,,,,,,,
>  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
>     Assignee: Dag H. Wanvik
>     Priority: Minor
>      Fix For:
>  Attachments: 611.diff, 611.stat, 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:
For more information on JIRA, see:

View raw message