Hey Brandon, Iterate over the _keys_ making sure the parent entity exists. You could design it to prevent rechecking for the same parent over and over, which will help reduce costs.
You can iterate over a lot of entities pretty fast with a keys-only query. Insert one task per X parents you need to check. You'll need to do some empirical testing, but I'd start with 500 or 1000, then do a single batch get for them. If any aren't found, remove the corresponding orphans. If you expect a lot of orphans, I'd use smaller groups. Robert On Sun, Feb 5, 2012 at 11:49, Brandon Donnelson <[email protected]> wrote: > Are there any slick datastore methods for Owned Collection orphan removal? > > Brandon Donnelson > http://c.gwt-examples.com > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/google-appengine/-/FvITFUJIbMcJ. > 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. -- 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.
