[
https://issues.apache.org/jira/browse/DERBY-4767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12897270#action_12897270
]
Yun Lee commented on DERBY-4767:
--------------------------------
I have a question about this. When I need change Derby client code to match
behavior with Embedded driver, does it mean that for this sql script,
CLIENT_RESULT_SET_NOT_OPEN(XCL16.S.1) should be replaced by
LANG_RESULT_SET_NOT_OPEN(XCL16.S.0)? And then, why did DERBY created two
different(but very similiar) messages?
> 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
>
> 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';
> 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.
