On Tue, 2007-01-16 at 23:55 +0300, Oleg Broytmann wrote: > On Tue, Jan 16, 2007 at 02:14:45PM -0500, David Turner wrote: > > The only way to prevent this is to lock the DB for writing before > > reading > > Not neccessary. There is "Serializeable" transaction isolation level.
Oh, right. That would do it. > > I am sure that we need to put inherited row creation inside a > > transaction > > What to do on a backend that lacks transaction support such as MySQL > with non-InnoDB tables? In that case, we cannot prevent other processes from screwing things up. But we can prevent SQLObject from doing so by using an ugly global lock. We can make that lock optional, so that if applications have a better idea, they can implement it. ------------------------------------------------------------------------- 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 sqlobject-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
