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: domain of lists@nabble.com designates
 216.139.236.158 as permitted sender)
Message-ID: <19379460.post@talk.nabble.com>
Date: Mon, 8 Sep 2008 12:33:37 -0700 (PDT)
From: derbyfan195 <huang195@gmail.com>
To: derby-user@db.apache.org
Subject: Does using DerbyDB require synchronization?
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


Just started using Derby in my Java code and realized some weird
synchronization issues. I have multiple threads accessing the same Derby
Database (embedded one) through a single connection. They issue read-only
queries, i.e., select, each with its own statement, and does some operations
on the returned ResultSet using ResultSet.next() operation. However, I
noticed sometimes, one of these next() calls would fail and gave me an error
of next() is not permitted, make sure that AUTO_COMMIT is turned OFF. I
don't know what this error means or why I need to turn AUTO_COMMIT off. Do I
need any synchronization among the statement objects obtained from the same
connection object? Any help would be appreciated.

-
Hai
-- 
View this message in context: http://www.nabble.com/Does-using-DerbyDB-require-synchronization--tp19379460p19379460.html
Sent from the Apache Derby Users mailing list archive at Nabble.com.