db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yun Lee (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-4777) perform different in Client and Embed modes when update on an invalid cursor
Date Mon, 16 Aug 2010 12:10:16 GMT

    [ https://issues.apache.org/jira/browse/DERBY-4777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12898869#action_12898869
] 

Yun Lee commented on DERBY-4777:
--------------------------------

In DERBY,  ERROR 42X30 (LANG_CURSOR_NOT_FOUND) occures in CurrentOfResultSet.getCursor() and
CurrentOfNode.bindNonVTITables(). While ERROR XJ202 (CURSOR_INVALID_NAME) occurs in Statement.setCursorName()
and Statement.flowExecute().

I think CURSOR_INVALID_NAME should just be used to show the 'name' of a cursor is invalid,
but not the cursor itself is invalid. If a cursor itselft is not invalid, a LANG_CURSOR_NOT_FOUND
is more suitable. 

> perform different in Client and Embed modes when update on an invalid cursor
> ----------------------------------------------------------------------------
>
>                 Key: DERBY-4777
>                 URL: https://issues.apache.org/jira/browse/DERBY-4777
>             Project: Derby
>          Issue Type: Improvement
>          Components: JDBC
>            Reporter: Yun Lee
>            Assignee: Yun Lee
>
> Consider the sql snippet below:
> create table test(c1 int, c2 int);
> insert into test values(1,1);
> update test set c1=2 where current of jdk4;
> for the 'update' line, we get 'ERROR XJ202: Invalid cursor name 'JDK4'. ' in Client mode,
while 'ERROR 42X30: Cursor 'JDK4' not found. Verify that autocommit is OFF.' in Embed mode.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message