Re: ACIDity of Prevayler 2.6

> I think like Robert that tx should be written only after being
successfully
> applied to the in-memory model.
>
> The change will not be visible if the tx is written in the same "lock
> scope" as the disk IO.

Yes. As I wrote here:
https://gist.github.com/1103582

"Applying transactions to the system before they are written will cause
queries to see unwritten changes. So, unless you sequence all queries with
disk writes, you lose the D in ACID.
Recovering the system after a transaction exception, even if done with the
RoyalFoodTaster pattern [and especially if restoring from disk], is a huge
hiccup in the system. If there is a silly transaction throwing a frequent
but unimportant exception, sysadmins will hate you for this feature.
Throwing an exception is just one particular kind of bug a transaction can
cause. All other bugs will not be caught, just as they won't be caught in
any DBMS."

I will organize a vote here next week on this rollback theme. I'm going
camping now. :)

See you, Klaus.

------------------------------------------------------------------------------
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