Hi Phil, Using CVS Head and ODMG, you can cast the ODMG Transaction object to TransactionExt, which provides a flush method. flush() sends out any pending SQL to the RDBMS without committing the transaction. That way you gain some coarse control on the order of SQL statements, which helps to avoid RI violations. It requires some experimenting, but so far it seems to work in all my problem cases.
Cheers, Gerhard On Wed, 22 Oct 2003 11:06:36 -0400, Phil Warrick <[EMAIL PROTECTED]> wrote: >Hi Gerhard, > >Could you elaborate? I've always run without constraints, but never >thought that it was a good idea to do so. > >Phil > >Gerhard Grosse wrote: > >> I just discovered that ((TransactionExt) tx).flush() might solve a lot >> of my problems... >> >> On Tue, 21 Oct 2003 16:57:30 +0200, Gerhard Grosse >> <[EMAIL PROTECTED]> wrote: >> >> >>>Hi, >>> >>>I just wonder what strategies others employ to avoid RI constraint >>>violations. It seems to me that these inevitably occur in larger >>>transactions on complex object models. Any hints other than turning RI >>>checking off altogether? (I'm short before doing so...) >>> >>>Thanks, >>>Gerhard >> >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
