[
http://issues.apache.org/jira/browse/DERBY-1251?page=comments#action_12378922 ]
Knut Anders Hatlen commented on DERBY-1251:
---
I will run some tests and commit the patch.
> cancelRowUpdates() affects rows updated with updateRow() in scrollable
>
[
http://issues.apache.org/jira/browse/DERBY-1251?page=comments#action_12378902 ]
Fernanda Pizzorno commented on DERBY-1251:
--
All of my comments have been addressed. The patch DERBY-1251v3.diff looks good.
> cancelRowUpdates() affects rows updated
[
http://issues.apache.org/jira/browse/DERBY-1251?page=comments#action_12378856 ]
Andreas Korneliussen commented on DERBY-1251:
-
> - //After a delete, the ResultSet will be positioned right before
> - //the next row.
> - rowData = null;
> - curre
[
http://issues.apache.org/jira/browse/DERBY-1251?page=comments#action_12378628 ]
Fernanda Pizzorno commented on DERBY-1251:
--
Review:
The patch looks good, here are some comments:
Index: java/engine/org/apache/derby/impl/jdbc/EmbedResultSet.java
=
[
http://issues.apache.org/jira/browse/DERBY-1251?page=comments#action_12377466 ]
Andreas Korneliussen commented on DERBY-1251:
-
Withdrawing the patch DERBY-1251.diff.
It turns out that the currentRow attribute in the EmbedResultSet may in certa
[
http://issues.apache.org/jira/browse/DERBY-1251?page=comments#action_12376245 ]
Andreas Korneliussen commented on DERBY-1251:
-
Actually, the previous comment indicates another related bug: after
updateRow(), rs.getXXX() returns the old value.
[
http://issues.apache.org/jira/browse/DERBY-1251?page=comments#action_12376218 ]
Andreas Korneliussen commented on DERBY-1251:
-
The bug was detected while adding the following testcase in SURTest:
/**
* Test that you can correctly run m
