On Apr 12, 4:18 pm, "Ikai L (Google)" <[email protected]> wrote: > No, it should be fine UNLESS you want to load all these child objects in a > single request. As a rule of thumb, load as little data as possible. You may > need to denormalize (the datastore isn't relational anyway) for additional > read performance.
To follow up on this, if a JDO owned relationship was used to support the 1:m relationship, would there be any way to *avoid* loading all the child objects together? The parent's list of children would be lazily fetched, so they would not be initially loaded with the parent. However, my understanding was that when the child list was accessed, this would load all the child objects. (So, if there were a large number of children, explicit key-based mgmt of the relationship might be a better route to take). -- 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 [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-java?hl=en.
