Hi Max,

I've just read your new post and I've got two questions.
1) should we discuss your new posts in this mailing list or in the blog?

Since you haven't answer my first question yet, :-P, I'm going to ask my second question in both ways.

2) Before your new post the only way I knew for transaction isolation was using the JDOCanRetryException (or at least we'll use it as soon as the bug fix about it will be released), now we've got also this JDOOptimisticVerificationException. Now, I can imagine the difference between them but I'd like to know what's the best way to deal with both of them. I mean, should we use both of them? Using the JDOCanRetryException mechanism shouldn't be need of the JDOOptimisticVerificationException.

We'd be very grateful if you could clarify this out.

Thanks

Max Ross wrote:
http://gae-java-persistence.blogspot.com/2009/10/optimistic-locking-with-version.html



--

Patrizio Munzi
Product Specialist
Viale Bruno Buozzi, 19 - 00197 Roma (Italy)
tel: +39 06 4543 3540
fax: +39 06 4543 3587
mobile: +39 393 7195 164
mail: patrizio.mu...@eris4.com
web: http://www.eris4.com
skype: eris4_munzi


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group.
To post to this group, send email to google-appengine-java@googlegroups.com
To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to