You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Dag H. Wanvik (JIRA)" <de...@db.apache.org> on 2006/10/10 18:57:22 UTC
[jira] Closed: (DERBY-1322) Missing resets of isOnInsertRow state
in net client when navigating away via other than ResultSet#next
[ http://issues.apache.org/jira/browse/DERBY-1322?page=all ]
Dag H. Wanvik closed DERBY-1322.
--------------------------------
> 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
> Issue Type: Bug
> Components: JDBC, Network Client
> Affects Versions: 10.2.1.6
> Reporter: Dag H. Wanvik
> Assigned To: Fernanda Pizzorno
> Priority: Minor
> Fix For: 10.2.1.6
>
> Attachments: derby-1322.diff, derby-1322.stat, derby-1322v2.diff, derby-1322v2.stat, Repro.java
>
>
> 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