I can't say much on if it would help to index the list twice but internally every search on a list property basically counts as a separate 'property = :1' search so it gets pretty big if you have huge lists.
On Sep 17, 3:16 am, Waldemar Kornewald <[EMAIL PROTECTED]> wrote: > Hi, > if I do multiple filter() calls on a ListProperty (e.g., with > SearchableModel) how is the result queried, internally? Do you run > multiple independent queries (one for each filter) and merge-join them > or is there an optimization? > > Let's assume the ridiculous case that the user enters two very common > words into the search form such that, say, 1/4th of the (huge) DB will > match each word and now we need the intersection of them both. Note > that I'm only interested in the first 300 results. Is the datastore > able to handle this case even with lots of entities in the DB? > > Would it help to index the list property twice? > > Thanks! > > Bye, > Waldemar Kornewald --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
