I misread (or missed?) one of your emails. Yes, makePersistentAll should be for inserts. I don't believe it was updated for updates. Here's the test I am looking at:
http://www.google.com/codesearch/p?hl=en#79kbA0UmWLw/trunk/tests/org/datanucleus/store/appengine/JDOBatchInsertTest.java&q=makepersistentall&sa=N&cd=4&ct=rc (note the lack of a test for batch update) It is expected behavior that the writes happen on close. Your issue is the double write. I'm wondering why JDO saves the objects - it shouldn't do this unless it detects that the objects have changed. -- Ikai Lan Developer Programs Engineer, Google App Engine Blogger: http://googleappengine.blogspot.com Reddit: http://www.reddit.com/r/appengine Twitter: http://twitter.com/app_engine On Fri, Oct 1, 2010 at 2:39 PM, Tommy <[email protected]> wrote: > Yes, we're using the latest SDK (1.3.7). > > I've attached a screenshot of the request. The objects corresponding to > the 6 puts were all sent to makePersistentAll(). According to the appstats, > put didn't get called for them until the persistence manager was closed at > the end of the transaction. Let me know if you need any more info or have > any suggestions for me to try. Thanks. > > > -- > 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]<google-appengine-java%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-appengine-java?hl=en. > -- 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.
