[
https://issues.apache.org/jira/browse/DERBY-4767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yun Lee updated DERBY-4767:
---------------------------
Attachment: derby-4765.patch
derby-4765.stat
Hi, Myrna. I have replaced CLIENT_RESULT_SET_NOT_OPEN by
LANG_RESULT_SET_NOT_OPEN with the suitable params and cretaed a testxcl16.sql
to test this issue. Please check the patch.
Besides, I have a question, CLIENT_RESULT_SET_NOT_OPEN is not used anywhere
now, except in SQLState.java, why not deleted it and change "XCL16.S.0" to
"XCL16.S"?
> 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
> Attachments: derby-4765.patch, derby-4765.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.
