On Jul 6, 10:58 pm, stefoid <stevenmath...@yahoo.com> wrote:
> But due to the large number of BOOKS that could be read by a USER, > and the large number of USERS who could be my friend, I cant > practically model BOOKS READ BY USERS and USERS WHO ARE MY FRIEND as > ListProperties... > > ...Because I would blow the 5000 index limit per entity, because each > value of ListPropery generates its own index entry. Is that correct? > you can have multiple ListProperty Entities per User, all in the same entity group. When you query, it will return a key if, say, the BOOK is in any of the associated lists. This is how I handle it. If one list approaches 5000 entries, I just spawn a new related list and start filling it instead. I really recommend you watch this I/O presentation closely. It basically spells out how to do this (better than I could hope to explain) http://sites.google.com/site/io/building-scalable-web-applications-with-google-app-engine -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appeng...@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
