This is going to show my predjudice about the recovery code, but at
least as described this seems so simple that I think there must be
something tricky going on.
To diagnose the issue you should enable the property to print all
queries to the derby.log, so that we can see if there is an unexpected
commit. If you can't find appropriate documentation on list or in docs
let the list know.
Definitely check how you are setting autocommit and make sure same
connection is used to do first insert and subsequent inserts - as
autocommit can be set on a per connection basis. Maybe good to describe
how you are turning autocommit off.
Mamta Satoor wrote:
Hi Gin,
From your description, it sounds like it might be a bug in Derby,
especially, since it works with other databases. A reproducible program
will definitely help establish that.
Mamta
On 6/3/05, *Gin Ng* <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote:
The code is just several inserts and then an explicit rollback. All
inserts
are successful, no SQL exception. The program is a unit test case which
does some database operations and then rollback the transaction to
get the
database back to the known state. The same program works with DB2 and
Oracle.
I cannot post the schema because it is quite big and complex. I have
been
trying to come up with a smaller test case to illustrate the
problem, but
still without succeed so far.
Thanks,
Gin Ng
Sunitha
Kambhampati
<
[EMAIL PROTECTED] To
l.com <http://l.com>> Derby Discussion
< [email protected]
<mailto:[email protected]>>
06/03/2005
03:38 cc
PM
Subject
Re: Rollback problem
Please respond to
"Derby
Discussion"
Gin Ng wrote:
>I have a table which is referenced by several other tables. When I
turn
>autocommit off, do the inserts to the tables and rollback. All
inserts are
>rolled back except the parent table. Anyone has encountered the
problem?
>
>Gin Ng
>
>
>
>
Can you provide more details on what you are trying to do so we can
figure out what is happening. Is there a chance you could post code that
shows this behavior ?
Also are you issuing an explicit rollback call or did an sql statement
generate an exception .
Thanks,
Sunitha.
