[jira] Commented: (DERBY-722) updateRow invalidates current row in result set

["Dag H. Wanvik (JIRA)" <de...@db.apache.org>]

    [ http://issues.apache.org/jira/browse/DERBY-722?page=comments#action_12358267 ] 

Dag H. Wanvik commented on DERBY-722:
-------------------------------------

Testcase "Positive Test3b" in lang/updatableResultset.java tests for
this situation and states:

"Since after updateRow(), ResultSet is positioned before the next row,
getXXX will fail".

So the behavior is expected for Derby, but why? For positioned update,
the position is kept.
(ANSI says so, too, cf. 2003, section 14.10 <update
statement:positioned>, General Rule 11: "CR remains positioned on its
current row,even if an exception condition is raised during evaluation
of any <update source>")

So why does Derby behave this way for updateRow() ?


> 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