[appengine-java] Re: Owned one-to-one relationships: cannot attach a new child to a parent which has already been saved

; Key key = keyBuilder.getKey(); graph.setId(key); indicatorPersited.setGraph(graph); pm.makePersistent(indicatorPersisted) But i'm still not satisfied because it's not what JDO is supposed to do on this own I may be wrong, so let me know...someone? no? ^^ On 16

[appengine-java] Re: Owned one-to-one relationships: cannot attach a new child to a parent which has already been saved

ships. > > On Apr 15, 1:07 pm, ckitop wrote: > > > Here, I've created a project that hosting the problem > > >http://code.google.com/p/testjdo/source/browse/#svn/trunk/TestJDO > > -Appengine sdk 1.3.2 > > -JUnit 3 > > > So, I made two unit tests t

[appengine-java] Re: Owned one-to-one relationships: cannot attach a new child to a parent which has already been saved

Here, I've created a project that hosting the problem http://code.google.com/p/testjdo/source/browse/#svn/trunk/TestJDO -Appengine sdk 1.3.2 -JUnit 3 So, I made two unit tests to test: Owned one-to-one relationships Owned one-to-many relationships -- You received this message because you are su

[appengine-java] Owned one-to-one relationships: cannot attach a new child to a parent which has already been saved

Hi, Configuration: - Appengine sdk 1.3.1 - 2 Entities: Indicator, Graph /* * INDICATOR.java */ @PersistenceCapable(identityType = IdentityType.APPLICATION, detachable = "true") @FetchGroup(name="graph", members = { @Persistent(name = "graph")}) public class Indicator { @PrimaryKey