This is both a bug and a limitation. The reported bug can be found as
datanucleus-appengine issue 80 (Recursive relation does not work) at:
Merci Didier.
--
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 google-appengine-java@googlegroups.com.
To unsubscribe from this group, send email to
Hi,
I think that it is still in the doc: see last bullet point of
http://code.google.com/appengine/docs/java/datastore/jdo/overview.html#Unsupported_Features_of_JDO
regards
didier
On Feb 6, 4:48 pm, Jan Willies j...@willies.info wrote:
2011/2/6 Cyrille Vincey crll...@gmail.com
Some time
Didier,
Do you mean There is currently *a bug* preventing owned one-to-many
relationships *where the parent and the child are the same class*, making it
difficult to model tree structures. This will be fixed in a future release.
You can work around this by storing explicit Key values for either
You cannot establish an owned relationship between two objects after the
child object (User in this case) has already been persisted. This is because
the parent key is embedded inside the child key, and keys can't be modified
once an entity is persisted in the datastore. You can, however, use an
I really recommend you read the documentation:
http://code.google.com/appengine/docs/java/datastore/overview.html
You are trying to do things the datastore does not allow. It's so
different that a relational datastore, I think you'll find you're
constantly roadblocked if you don't become
