[
https://issues.apache.org/jira/browse/DERBY-3839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12702051#action_12702051
]
Tiago R. Espinha commented on DERBY-3839:
-----------------------------------------
After talking this over on IRC, Dag suggested something that fixed this issue.
This test is using the following parameters on the createStatement:
ResultSet.TYPE_SCROLL_INSENSITIVE, ResultSet.CONCUR_UPDATABLE and
ResultSet.HOLD_CURSORS_OVER_COMMIT
After going through the ResultSet code, I found out that the
checkForUpdatableResultSet() method (called upon the deleteRow() ) overrides
any of the checks that it would do, unless the ResultSet is set as
CONCUR_READ_ONLY. So, basically put, switching this parameter will make the
repro pass.
I am still working on the actual test and at this point I decided that it would
be a better option to create individual tables for each test.
(As suggested by Kathey here: http://tinyurl.com/dxozhb )
Finally, I am also opening a bug for the described behavior above.
> Convert
> "org.apache.derbyTesting.functionTests.tests.store.holdCursorJDBC30.sql" to
> junit.
> -------------------------------------------------------------------------------------------
>
> Key: DERBY-3839
> URL: https://issues.apache.org/jira/browse/DERBY-3839
> Project: Derby
> Issue Type: Test
> Components: Test
> Reporter: Junjie Peng
> Assignee: Tiago R. Espinha
> Attachments: derby-3839-1.patch, derby-3839-1.stat, derby-3839.patch,
> ReproHoldCursorBug.java
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
