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-722) updateRow invalidates current row in result set
Date Tue, 22 Nov 2005 01:08:42 GMT
     [ http://issues.apache.org/jira/browse/DERBY-722?page=all ]

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

    Attachment: Main.java

> updateRow invalidates current row in result set
> -----------------------------------------------
>
>          Key: DERBY-722
>          URL: http://issues.apache.org/jira/browse/DERBY-722
>      Project: Derby
>         Type: Bug
>   Components: Network Client, JDBC
>     Versions: 10.1.2.2, 10.1.3.0, 10.2.0.0, 10.1.2.1, 10.1.2.0, 10.1.1.2, 10.1.1.1, 10.1.1.0
>  Environment: Sun JDK 1.4.2, Solaris 10
>     Reporter: Dag H. Wanvik
>     Priority: Minor
>  Attachments: Main.java
>
> In both the network and embedded drivers, after an updateRow has been performed,
> reading the current row fails. A new next() is required to get a new valid position,
as shown by the attached repro. 
> In contrast to the case for deleteRow, JDBC does not require a repositioning after an
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


Mime
View raw message