You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Myrna van Lunteren (JIRA)" <ji...@apache.org> on 2010/08/16 20:48:20 UTC
[jira] Reopened: (DERBY-4767) Detailed prompt for Error XCL16 is
different between Client and Embed
[ https://issues.apache.org/jira/browse/DERBY-4767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Myrna van Lunteren reopened DERBY-4767:
---------------------------------------
I decided to add anoter check to one more test - jdbcapi.ClosedObjectTest - and it showed that the findColumnX method in client/am/ResultSet was called not just from findColumn, but a number of other methods. So, passing on 'findColumn' was not the right thing to do there. Instead, I'm adding a parameter to the method and passing in the appropriate operation for each time the findColumnX method is called.
Also, this added check in ClosedObjectTest showed one more incorrect string in code not touched by the original patch, in impl.jdbc.EmbedResultSet, method rowDeleted(), the string passed on to the LANG_RESULT_SET_NOT_OPEN is "rowUpdated".
I'll fix up these issues, run tests and if this shows no further trouble, I'll commit.
> 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.