Optimistic transactions sets a version on the object. If something is deleted in another thread then JDOOptimisticVerificationException is thrown when you update. THat's the whole point of optimistic txns (whether in JDO, JPA or anywhere).
And no, after reading an object in via getObjectById the object is managed, and so any update will go to the DB without any makePersistent call being needed (obviously in the ancient version of DataNucleus you have there it will wait til the next txn before it does (or just put the pm.getObjectById+update in a txn). -- 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 [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
