On Mon, Dec 11, 2006 at 04:16:23PM -0500, David Turner wrote:
> > Because accessing the DB during row creation when the "row" is actually
> > a set of rows exposes the inconsistent state of the DB, and SQLObject
> > certainly cannot prevent this.
>
> Sure it can -- using transactions in the way I suggested
But that's up to the user program, because it is the user program that
overrides the function to calculate the default.
> or using a
> liveness marker which is atomically set at the end of creation. Either
> of these would work.
Patches could be submitted to the SF tracker.
Oleg.
--
Oleg Broytmann http://phd.pp.ru/ [EMAIL PROTECTED]
Programmers don't die, they just GOSUB without RETURN.
-------------------------------------------------------------------------
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
