Re: ACIDity of Prevayler 2.6

On Nov 14, 2012, at 7:07 PM, Klaus Wuestefeld wrote:

> What if the food taster were in place but instead of
> somethingThatGoesWrong() you do:
> 
>   if ("".isEmpty()) return;

I would say that the expected behavior of that code would be breaking out of the transaction, not aborting it.  If you insinuate that it's bad code I can only agree, but I don't see the point you try to make. 

If only parts of a transaction is committed due to an error, internal or external, it's not an atomic commit as far as I've been taught. Thus I would say that if the code above demonstrates any given human error that causes the transaction to not execute fully then no, it's not an atomic commit in a philosophical sense although the framework would allow for a atomic commit in theory.

But as far as I've been taught, Prevayler no longer is a framework that allows for atomic transaction commits. And I have no problems with that.



		karl
------------------------------------------------------------------------------
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications!
http://p.sf.net/sfu/zoho_dev2dev_nov
_______________________________________________
To unsubscribe go to the end of this page: http://lists.sourceforge.net/lists/listinfo/prevayler-discussion
_______________________________________________
"Databases in Memoriam" -- http://www.prevayler.org