[
https://issues.apache.org/jira/browse/DERBY-4767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12898661#action_12898661
]
Myrna van Lunteren commented on DERBY-4767:
-------------------------------------------
committed the change I mentioned above - passing in 'update' instead of 'next'
in the getPositionedUpdateResultSet method in client.am.sectionManager with
revision 985613.
> Detailed prompt for Error XCL16 is different between Client and Embed
> ---------------------------------------------------------------------
>
> Key: DERBY-4767
> URL: https://issues.apache.org/jira/browse/DERBY-4767
> Project: Derby
> Issue Type: Improvement
> Components: JDBC
> Reporter: Yun Lee
> Assignee: Yun Lee
> Fix For: 10.7.0.0
>
> Attachments: derby-4767-1.patch, derby-4767-1.stat, derby-4767.patch,
> derby-4767.stat
>
>
> For the sql script below:
> create table t1(c11 int, c12 int);
> -- insert data into tables
> insert into t1 values(1,1);
> insert into t1 values(2,2);
> -- set autocommit off
> autocommit off;
> get with nohold cursor jdk1 as 'SELECT * FROM t1';
> -- do fetches from the cursor
> next jdk1;
> --commit
> commit;
> -- now try the fetch on cursor again after commit
> -- cursors jdk1 will give Error XCL16
> next jdk1;
> -- clean up.
> close jdk1;
> for the line "next jdk1;", an Error XCL16 will be thrown. However, detailed
> prompt for Error XCL16 is different between Client and Embed.
> In client mode, we get "ERROR XCL16: ResultSet not open. Verify that
> autocommit is OFF."
> While, in embed mode, we get "ERROR XCL16: ResultSet not open. Operation
> 'next' not permitted. Verify that autocommit is OFF."
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
