[
https://issues.apache.org/jira/browse/DERBY-3839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tiago R. Espinha updated DERBY-3839:
------------------------------------
Attachment: ReproHoldCursorBug.java
I have run into what seems to be another bug.
Initially I thought this could simply be a normal different behaviour between
embedded and client drivers. Kathey has however suggested that it could be a
bug so I'm posting it here to get some opinions.
The issue is on the embedded driver. The problem happens when we create a
cursor and while having it on a certain record, another statement is executed
that deletes both the record that the cursor is on and the next one. If
afterwards we advance the cursor, the embedded driver will act as if the rows
haven't been deleted at all, whereas the client driver seems to behave
correctly.
It needs to be said though that the client driver will only pass as long as the
bulkFetchDefault is set to 1. Any other values on this property seem to make
the client error out as well.
> 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, ReproHoldCursorBug.java, ReproHoldCursorBug.java
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
