[ http://issues.apache.org/jira/browse/DERBY-611?page=all ]

Dag H. Wanvik updated DERBY-611:
--------------------------------

    Attachment: 611.diff

An updated diff, which removes a spurious blank line introduced by the
first version of the patch.

The reviewer (Bernt) asked for explanation of the removed usage of the
variable 'chainAutoCommit': It was used to be able to potentially
append an commit action onto the update/delete row action to be sent
to the server over DRDA, in the case that autocommit is in force, and
to anticipate a reply from that commit action.  Since the intention of
the patch is to remove this commit, the variable is no longer in use
and has been removed.

> 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: 10.1.1.0, 10.1.1.1, 10.1.1.2, 10.1.2.0, 10.1.2.1, 10.2.0.0, 
> 10.1.3.0, 10.1.2.2, 10.0.2.2
>  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: 10.2.0.0
>  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:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

Reply via email to