Hi, Thanks for the response.
Just to clarify, if the query has an order by clause say order by date DESC or there is an inequality filter on a field 'other than' the StringListProperty field than a composite index would be created which would lead to an exploding index condition on queries like"words=1, words=3, words=5" that might match a single row. Also, > for you). Note that if the data is too sparse (too many rows scanned without > finding results), the merge-join query may quit and instruct you to use a > custom index instead. > how is the above 'instruction' made? Say I had 1 million rows each with a 500 item StringListProperty and a query that would maybe match say 2 rows would that trigger such an instruction. Thanks S. Sriram --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
