Closed GoogleCodeExporter closed 8 years ago
Same as issue 165. The GAE/J plugin persistence process is way too fragile and
doesn't have any handling for bidirectional relations where the keys are
generated in-datastore. Should check if bidir and the parent is not yet
inserted and put it without the relation, then put the child, then update the
parent. Issue 165 has the same thing but using a String PK field
Original comment by googleco...@yahoo.co.uk
on 14 Aug 2011 at 8:12
The problem here is that if you persist the "mapped" side of a 1-1 bidir (i.e
the part that *doesn't* own the relation ... in your case Parent2 ... then the
GAE/J plugin has no idea what to do and expects the "owner" of the relation
(i.e child) to be persistent when it receives the persist of parent.. If you
instead call pm.makePersistent(c) then it works. IMHO it's crap handling in the
GAE/J plugin and ought to cope with whichever side of a relation is being
persisted ... and just set the "parent" of the EntityGroup to be the object
passed in to persist.
Original comment by googleco...@yahoo.co.uk
on 19 Aug 2011 at 1:48
Original issue reported on code.google.com by
ja...@bobberinteractive.com
on 22 Mar 2011 at 9:14Attachments: