Hello chaps, I've been sifting through the JDO docs to try to understand what behaviour I will see if I use makePersistentAll with a bunch of PersistenceCapable objects when some may already exist in the datastore (with the objects in the Collection for makePersistentAll having the same Key as in the datastore).
I'm writing an App Engine app with a GWT front end and have created cutdown IsSerialisable object versions of my PersistenceCapable objects. Because of the GWT interaction I need to retrieve the PersistenceCapable object, transform it into an IsSerialisable object, do some stuff in the front end, and then store changes in the service servlet. I'd like to avoid having to lookup the object using the Key and then updating it, and was wondering if I could get away with using the makePersistentAll method as a shortcut. The docs seem to imply I could do this if the object was detached, but not sure how it would behave if it was a re-constructed representation of the PersistenceCapable object as opposed to one retrieved directly from the datastore. Any guidance would be greatly appreciated! Thanks Gemma -- 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-j...@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.
