Dnia czwartek, 11 listopada 2004 13:49, Gerhard Grosse napisał: > On Wed, 10 Nov 2004 21:26:22 +0100, Grzegorz Pypec <[EMAIL PROTECTED]> > > wrote:
> > Instead of tx.checkpoint() you can use ((TransactionExt) tx).flush(), > which flushes all SQL to the DB without commit. > > However, normally OJB does a pretty good job in ordering the SQL > correctly. Could it be that you have some cyclic references in your > object model (e.g. A->B and B->A)? > > Gerhard I suppose that after invoking flush(), transaction holds db connection opened all the time so we can later rollback? From JavaDoc: "Calling flush flushes persistent object modifications made within the ODMG transaction since the last checkpoint to the underlying database transaction" If so, it is not a good news :) Is anyone has similar problem with deleting referenced objects? I have exactly the same problem as Grzegorz Pypec with ojb1.0.1 nad PostgreSQL 7.4 (jdbc 3.0 drv). I can't believe that such essential feature doesn't work. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
