I'm glad that you have fixed your problem. I made the decision very early on to detach everything always (unless I was actually in the middle of persisting data within a method). This might be inefficient, but it does seem to work for my brain!
On Jul 22, 2:18 pm, Christian Gruber <[email protected]> wrote: > On Jul 21, 2:43 am, Ian Marshall <[email protected]> wrote: > > > I use > > @PersistenceCapable(identityType = IdentityType.APPLICATION, detachable = > > "true") > > Hey Ian. Sorry, I had left that off the example - I also use > @Per...Cap... with the options you identified. > > However, I have solved it. > > It seems that I had a back-relationship with "mapped-by" and added a > backlink, which I didn't need, but the big thing seems to be that when > I was fetching these entities, I did not detach them. > > So I got my persistence manager to do something like... > > pm.setDetachAllOnCommit(true); > tx.begin(); > ... > tx.commit(); > > (or whatever). > > it's the either individually detaching or bulk detaching that wasn't > working. Somehow some internal state in the PM was being messed up by > my passing around non-detached persistent entities between > transactions. > > cheers, > Christian -- 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.
