Re: Prevayler - update data

1 nov 2012 kl. 21:28 skrev Naveen Chawla:

> Although it's not part of the "baptism problem", any change to the prevalent object outside of any transaction is also not recoverable. So I like to simplify it by just thinking "stick to prevalentSystem (when making changes)" (while picturing the "prevalentSystem" parameter in a Transaction's "executeOn" method). This may or may not help.

Good catch, I'll make e105 demonstrate this!

> If you are doing a manual (nice), my criteria would be as short (few words) as humanly possible and using only code snippets, also as brief as humanly possible, which highlight only the relevant bits, between paragraphs, instead of linking to full code files. This may or may not be what you want to do, but it's just my opinion.

I agree. In fact I already feel that some of the text in the README.md:s are a bit too much. In particular I feel that the e103 is hard to read.

Thanks!


		karl


------------------------------------------------------------------------------
LogMeIn Central: Instant, anywhere, Remote PC access and management.
Stay in control, update software, and manage PCs from one command center
Diagnose problems and improve visibility into emerging IT issues
Automate, monitor and manage. Do more in less time with Central
http://p.sf.net/sfu/logmein12331_d2d
_______________________________________________
To unsubscribe go to the end of this page: http://lists.sourceforge.net/lists/listinfo/prevayler-discussion
_______________________________________________
"Databases in Memoriam" -- http://www.prevayler.org