Re: ACIDity of Prevayler 2.6

4 dec 2012 kl. 18:06 skrev Klaus Wuestefeld:

>> Sadly, that product did not make it to market and a portion of the
>> reason was that the decision makers were not comfortable with
>> an entirely new data system that did not have the same level of
>> commitment to data protection that RDBMSs claim.
> 
> Were they happy and confident with Prevayler with the FoodTaster
> (rollback on exceptions)?


This discussion has wandered quite a bit from the original can of worms I opened up. 

I sent the original mail in this thread because I think it's a horrid idea to claim Prevayler is something it might not be.  I'm pretty sure that a thread with 50+ mails in a few days on a list that normally yield a handful per year is strong evidence for us having at least controversy on our hands.

Let me sum up what I think me and a few others tried to say: 
We will not give the ACID stamp of approval to a persistency layer that lacks possibility to rollback a half baked transaction that managed to execute some changes to the persistent data. This is according to us the very definition of all-or-nothing. 


I'm afraid that I still don't understand what the arguments of those that do not share the opinion that rollback is required.  Is it simply that you state rollback is not a required feature for ACIDity? Or perhaps that rollback is not a required feature of ACID in Prevayler due to a transaction in Prevayler is something quite different than a transaction in other systems? Or is it something completely different? Could someone please try to sum it up for me in a sentence or two?

While re-reading the complete thread I noticed that almost all the posts are hung up on the food taster. In my opening post I didn't mean to say that the food taster was the solution, all I ment to say is that the food taster indeed supplied built in rollback functionality and now there is no such built in feature. If rollback is required now then it must be manually written by the person that implements the transaction. Several  hypothetical alternative solutions for rollback out of the box has been presented in this thread, but as I've written in all my previous posts I don't give a rat's ass wether or not  Prevayler does rollbacks out of the box,  pass the test for ACIDity or what not since it works great as is. I've never had any problems even though I've been running some rather large implementations with heavy user load and millions of transactions per day. 

I just think it's a horrid idea to claim Prevayler is something it might not be.  


		karl

------------------------------------------------------------------------------
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d

_______________________________________________
To unsubscribe go to the end of this page: http://lists.sourceforge.net/lists/listinfo/prevayler-discussion
_______________________________________________
"Databases in Memoriam" -- http://www.prevayler.org