Re: ACIDity of Prevayler 2.6

hakan eryargi <[email protected]> Thu, 15 Nov 2012 17:00:55 +0200
Newsgroups gmane.comp.java.prevayler
Message-ID <CAPg-4YVrEiHEHvqv_kFwZOvLq7mJ47-eqzWo_vyo-FGViE098A@mail.gmail.com>
ACID properties may depend on each other but they are still different
properties.

I think the point is that different classes of errors affect different
> aspects. Resiliency in the face of power fail is about atomicity - you
> won't write half a txn. Resiliency in the face of other errors can be about
> consistency. For example, consider concurrency conflicts - are they
> flagging a break of atomicity or consistency ?
>

IMHO, recovering the transaction after power fail is durability. Running
that transaction atomically is atomicity, but that has no direct relation
with power fail or recovery.

A concurrency conflict is itself neither an atomicity nor consistency
break. If it happens in the middle of a transaction and framework dont take
changes back, then it's an atomicity break but this is not related to the
nature of concurrency conflict. From a higher perspective it's just a type
of failure that breaks framework's atomicity. Same applies to consistency.

Hakan

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