Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Discussion" <derby-user@db.apache.org>
Received-SPF: pass (athena.apache.org: local policy)
From: dag.wanvik@oracle.com (Dag H. Wanvik)
To: Derby Discussion <derby-user@db.apache.org>
Subject: Re: java.lang.RuntimeException: java.sql.SQLException: ResultSet not
 open
References: <AANLkTikjxrjpyMad70xqAxuVfdMNzFvgUebcjk8W7ZoC@mail.gmail.com>
Date: Fri, 29 Oct 2010 05:24:49 +0200
In-Reply-To: <AANLkTikjxrjpyMad70xqAxuVfdMNzFvgUebcjk8W7ZoC@mail.gmail.com>
	(Veresh Jain's message of "Thu, 28 Oct 2010 16:51:45 -0700")
Message-ID: <x1oxlj5hptoe.fsf@oracle.com>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (usg-unix-v)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

Veresh Jain <vereshjain@gmail.com> writes:

Hi Veresh, this questions belongs on the Derby user's list. This list if
for development issue.

As to your question, the fact that other databases work, doesn't mean
Derby is wrong, please provide som more detail about what you are doing.

For example if you are using autocommit and have two open result sets in
that transaction, when the first one is drained it is automaticaly
closed leading the the transaction to commit as well, somewhat
surprisingly, perhaps. In such cases, run with autocommit off for best results.

Dag

> Hi,
>
> We are using Apache Derby latest version in our project and is getting error
> "java.lang.RuntimeException: java.sql.SQLException: ResultSet not open.
> Verify that autocommit is OFF."
> Same SQL statement works properly with MySQL and Oracle but DErby it fails.
>
> Please provide any pointers as what could be wrong.
>
> Thanks a lot.
>
> Regards
> Veresh

--