Fair points. It's up to you of course. I hadn't thought about cascade deletes.
Possibility to query child entities for parent key -------------------------------------------------- Max Ross's GAE persistence blog may mention something about this. It's been a long while since I read the possibly-relevant post. -------- Original Message -------- Subject: [appengine-java] Re: Entity-User-Permission modelling with JDO. Help! Date: Mon, 19 Dec 2011 08:32:34 -0800 (PST) From: Chuck Lega <chuck.l...@gmail.com> Reply-To: google-appengine-java@googlegroups.com To: google-appengine-java@googlegroups.com Hmm, interesting, since the link of the doc can be queried (for "what docs to I have permissions on). Clearly it is a good idea to have this link pointing back to the doc (maybe even bidirectional JDO "mappedBy" if possible for a list). I guess what would be really great would be the possibility to query child entities for parent key. But that is not supported, right? But what is won from having these entities unowned instead of a list owned by the document entity? I see the point in being able to query for document keys, but with an owned entity cascade delete is for free. JDO will make this "list" into separate entities in db anyhow? -- 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 google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
