With millions of children, you don't want to model the 1:m relationship with a parent list property. Instead, you can include in the child entities a Key property pointing to the parent. Then, to find children of a given parent, you can do a query on the children that filters on that parent key.
(Note that with that many children, it most likely does not make sense to define the children as actually in the same entity group as the parent-- there could be lots of contention issues if different requests need to modify different children). On Fri, Feb 17, 2012 at 1:16 PM, hendrix.jason <[email protected]>wrote: > If I have a @PersistenceCapable class that contains a List of another > @PersistenceCapable class, and that List is millions of items in size, > is that OK? > > Does that exceed a maximum for Java's List size? > > What is the best way for a parent to have millions of children and > still have it easy to add new ones without loading tons of data in to > memory? > > -- > 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. > > -- 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.
