[ http://issues.apache.org/jira/browse/DERBY-1322?page=all ]
Fernanda Pizzorno updated DERBY-1322:
-------------------------------------
Attachment: derby-1322.diff
derby-1322.stat
Changes in patch derby-1322.diff:
java/client/org/apache/derby/client/am/ResultSet.java
Moved part of the method moveToCurrentRow() into a new method
moveToCurrentRowX() and added a call to moveToCurrentRowX() from all
positioning methods.
java/testing/org/apache/derbyTesting/functionTests/tests/jdbcapi/SURTest.java
Added a test case.
I have run derbyall, two tests failed but it did not seem to be related to this
patch. Can someone please review this patch?
Thank you in advance!
> 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
>
> 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
