By the way, have a look at: http://devblog.miumeet.com/2011/08/much-more-efficient-implementation-of.html
It's much more efficient than db.ListProperty(int) Cheers, -Andrin On Thu, Jul 28, 2011 at 6:17 PM, Pascal Voitot Dev < [email protected]> wrote: > good idea also :) > > > On Wed, Jul 27, 2011 at 7:17 PM, Ernesto Oltra <[email protected]>wrote: > >> And for followers, you could too shard the lists. You can have several >> entities, each with, about 100 results or so (or 1000, or 2000, I prefer 100 >> for easy of serializing/deserializing). All these would have the user as >> ancestor. When listing, take only one entity, deserializing its lists (only >> 100 results) and show some of them. When listing all, you can use cursors >> and some tricks to have the job done (job = paging =) ) >> >> -- >> 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/-/tRQCOATsWdUJ. >> >> 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. > -- 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.
