Re: New to Prevayler: "Baptism problem" basics?

Does anybody have the answers to these questions?

On Sep 9, 2011 4:53 PM, "Naveen Chawla" <[email protected]> wrote:

That's brilliant, Klaus! So can I do as many
direct-field-access modifications, and on as many levels as I like, on my
"prevaylerSystem"-derived object, one-after-the-other, within a
single Transaction ("executeOn()"), or am I restricted to just one line of
change per transaction?
All the sub-objects must also implement Serializable, yes?

So this "baptism problem" isn't really a problem at all?! I'm surprised
not to have read "As long as your object's from "prevaylerSystem" you're
good to go" about how to avoid the "baptism problem".

Am I right that this only applies to making changes and not to queries? Even
so, do you recommend using "Query" for every access as a replacement for
all direct access? Does doing so de-necessitate any and all concurrency
control? If I had no concurrency control of my own, in what sorts of cases
would I be ok to use direct access instead of using Query?

By the way, Klaus, I cannot put into words how great I think you are.

On 9 September 2011 15:07, Klaus Wuestefeld <[email protected]> wrote: > > Yes.
> > > On Fri, Sep 9, 20...

------------------------------------------------------------------------------
Malware Security Report: Protecting Your Business, Customers, and the 
Bottom Line. Protect your business and customers by understanding the 
threat from malware and how it can impact your online business. 
http://www.accelacomm.com/jaw/sfnl/114/51427462/

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