@Rick, JDO doesn't encourage you to do anything, nor impose it. Perhaps its just that some will, upon using it, think in a particular way because they used a similar API before, and they're used to their "good old" RDBMS handling things for them so assume the same is true ... and it isn't as you say. Doesn't mean they can't bundle things together with JDO to minimise query impact also.
@Peter, You observe behaviour in a very old version of software, and nontransactional operations in that version did things differently (though still comparable to the likes of Hibernate). The v2 version of Googles plugin makes use of recent software and all nontransactional persists/deletes are atomic. Obviously you could just put things in a transaction and you'd be fine too. Read about caches here http://www.datanucleus.org/products/accessplatform_3_0/jdo/cache.html -- 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.
