What code are you using to detach the entities? If you're just calling setDetachAllOnCommit, then yes, this requires a transaction. If you don't use transactions, then you can do something like this:
obj = pm.getObjectById(Object.class, key); obj = pm.detachCopy(obj); There's a similar detachCopyAll for detaching Collections. I use these in my own applications and they work fine. - Jason On Thu, Sep 3, 2009 at 11:28 AM, Esteban Masoero <[email protected]>wrote: > > Hi there, > > I'm having a problem similar to the one described here > > http://groups.google.com/group/google-appengine-java/browse_thread/thread/54c5c1e1ec1b3ff0/bcb54506ed134654?l > , > but using JDO instead of JPA. > Instead of fetching the object in a "normal" way, I fetched it inside a > transaction and it worked fine (the object was properly detached). > > Should an issue be reported? or is this problem addressed by the the > issue 1906 > (http://code.google.com/p/googleappengine/issues/detail?id=1906)? (I ask > it because as I see, the exceptions thrown by that JPA-examble are jdo > exceptions, so it gives me the feeling that JDO and JPA share some > components, and consequently it would be the same bug.) > > Thanks, > > Esteban > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
