Forget about this way : even if this having millions of children entities for one ancestor is theoretically feasible, you'll hit a write performance issue when you generate those entities : only 1 write / second in one given entity group (ancestor).
On 17 fév, 03:16, "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.
