I normally leave autocommit turned on, but in a few places in my code I
wrap multiquery transactions like this:
try {
setAutoCommit(false);
... // do a bunch of related updates
}
finally {
commit();
setAutoCommit(true);
}
Is this the right way to do it, and would the behaviour I see have to be
c
On 06/10/2010 14:57, Bryan Pendleton wrote:
It does take a bit of practice to learn how to read the information,
although I suspect you're not looking for basic introductory info
at this point. Still, this is a place to start:
http://wiki.apache.org/db-derby/LockDebugging
OK, thanks. I've had
On 10/6/2010 12:07 AM, Mamatha Kodigehalli Venkatesh wrote:
Hello all,
Below is the ddl for the table that I created using 10.5.3. When arecord is
inserted into tidlrblt table trigger- gls_blt_trg will push a corresponding
record into tidlggls table
Hi Mamatha,
I am able to reproduce th
wrong problem. I don't really understand the details of what the
lock table dump is telling me,
It does take a bit of practice to learn how to read the information,
although I suspect you're not looking for basic introductory info
at this point. Still, this is a place to start:
http://wiki.apac
I am using Derby 10.5.3 and am having occasional locking problems which
result in a RollbackExpection ("a lock could not be obtained within the
time requested") when deleting registration information from one of my
tables. Each user can be a member of multiple groups, and the table of
registration
Hello,
My name is Mike Parente - I'm looking for Apache Derby Database training for
the US Air Force.
Can you tell me if there is formal classroom training available?
Thank you,
mike
Michael Parente
President/Founder
Veteran-Owned VOSB
Integrated Training Solutions, Inc. - T
Hello all,
Below is the ddl for the table that I created using 10.5.3. When arecord is
inserted into tidlrblt table trigger- gls_blt_trg will push a corresponding
record into tidlggls table
CREATE TABLE tidlrblt
(
blt_number INTEGER NOT NULL GENERATED ALWAYS AS IDENTITY (START WITH 1
