Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <11820073.306061281624736813.JavaMail.jira@thor>
Date: Thu, 12 Aug 2010 10:52:16 -0400 (EDT)
From: "Yun Lee (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Updated: (DERBY-4767) Detailed prompt for Error XCL16 is
 different between Client and Embed
In-Reply-To: <32539561.275801281534737300.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-4767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Yun Lee updated DERBY-4767:
---------------------------

    Attachment:     (was: derby-4765.stat)

> 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-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.