Read the section of the docs Stephen gave a link to (re exploding indexes). Your problem is that all of those indexes on the list property are 'exploding'. Your query might be able to use only the built-in single property indexes (via merge-join), if you weren't also ordering. If you search the groups a bit you can find a lot of discussion on the topic.
Entities are implicitly ordered by key, so perhaps you can incorporate the submit date into the key-name, then remove the order clause and all of those composite indexes. Or, wait and hope the next-gen queries stuff gets implemented soon so that you can remove the composite indexes. Robert On Thu, Apr 28, 2011 at 15:29, ZS <zimon.spa...@gmail.com> wrote: > Now max. 5 tags, good! > > Sorry but, what is the best way to build a tags system on AppEngine? > > -- > 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-appengine@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. > -- 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-appengine@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.
