Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <7135501.494401282484121459.JavaMail.jira@thor>
Date: Sun, 22 Aug 2010 09:35:21 -0400 (EDT)
From: "Yun Lee (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Updated: (DERBY-4777) Different behavior in Client and
 Embedded modes when update on an invalid cursor
In-Reply-To: <20373260.363161281959956198.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/DERBY-4777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Yun Lee updated DERBY-4777:
---------------------------

    Attachment: derby-4777-releasenote.patch
                derby-4777-releasenote.stat

A patch for releasenote.html is submitted, please check it, thanks!

> Different behavior in Client and Embedded 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
>    Affects Versions: 10.7.0.0
>            Reporter: Yun Lee
>            Assignee: Yun Lee
>         Attachments: derby-4777-releasenote.patch, derby-4777-releasenote.stat, derby-4777.patch, derby-4777.stat, DERBY-4777_b.diff, DERBY-4777_b.stat
>
>
> 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.