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] Commented: (DERBY-1322) Missing resets of isOnInsertRow state in net client when navigating away via other than ResultSet#next
Date Tue, 23 May 2006 23:35:31 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1322?page=comments#action_12413030 ] 

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

Thanks for addressing my comments! I think it is ready to go.


> Missing resets of isOnInsertRow state in net client when navigating away via other than
ResultSet#next
> ------------------------------------------------------------------------------------------------------
>
>          Key: DERBY-1322
>          URL: http://issues.apache.org/jira/browse/DERBY-1322
>      Project: Derby
>         Type: Bug

>   Components: JDBC, Network Client
>     Versions: 10.2.0.0
>     Reporter: Dag H. Wanvik
>     Assignee: Fernanda Pizzorno
>     Priority: Minor
>      Fix For: 10.2.0.0
>  Attachments: Repro.java, derby-1322.diff, derby-1322.stat, derby-1322v2.diff, derby-1322v2.stat
>
> Please see the enclosed repro program.
> When attempting the deleteRow, it will fail with SQL state 24000 "no
> current row", since the first() call doesn't properly reset the
> IsOnInsertRow_ state. By inspection of ../am/ResultSet.java I found
> the other positioning calls beside next and moveToCurrentRow to suffer
> the same problem.

-- 
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