ok i answered it myself I had no idia my collections were being persisted by default even though i wasn't specifying. adding decoration @NotPersistent fixed it
I actually don't really like this feature: Tip: JDO specifies that fields of certain types are persistent by default if neither the @Persistent nor @NotPersistent annotations are specified, and fields of all other types are not persistent by default. See the DataNucleus documentation for a complete description of this behavior. Because not all of the App Engine datastore core value types are persistent by default according to the JDO specification, we recommend explicitly annotating fields as @Persistent or @NotPersistent to make it clear. On Oct 19, 11:13 am, Benjamin <[email protected]> wrote: > If i have objects A and B - and I don't have any parent child > relationships set up. I can make A and B objects persist easily. > > If I add a property A that is a list of B without any @Persistent or > mapping decoration, just a plain old empty collection property for > later use during run time, I can no longer add B objects to the > datastore, just becuase A has a list of B > > A a = new A() > pm.makePersistent(a); > > B b = new B() > pm.makePersistent(b); > > both show up in datastore > > if i add > public List<B> blist; to class A > > B b = new B() > pm.makePersistent(b); > fails - no error, just b is not in the store when i go look for it. > > what's going on? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" 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?hl=en -~----------~----~----~----~------~----~------~--~---
