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 19:16:47 GMT
     [ http://issues.apache.org/jira/browse/DERBY-611?page=all ]

Dag H. Wanvik updated DERBY-611:

    Attachment: 611.diff.3

Uploaded a new version of the patch which adds an extra test case as
suggested by Mamta in this mail:


> 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.3, 611.stat.3, 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