On Mon, 2006-12-11 at 22:53 +0300, Oleg Broytmann wrote: > On Mon, Dec 11, 2006 at 02:47:05PM -0500, David Turner wrote: > > There's a bit of a tricky thing about transactions: we need to make sure > > that the calculation of default values for the derived row takes place > > outside (but simultaneous with) the transaction, because anything inside > > the transaction can see the new row in the base table. > > Certainly, anything inside the transaction can see the new rows, but I > do not see anything tricky here. The user's program doesn't have control > until SQLObject fully create all rows, so what is the problem?
This is not quite true, if I understand correctly. First, sqlobject creates the base row, then (if necessary) it calls methods to get default values for the derived class, then it creates the derived row. So the user's program does have control during those methods (and this is where I ran into the problem). ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ sqlobject-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
