as long as you filter on the same property you don't need an explicit index because it uses the automatic indexes. if you filter on 2+ different properties you need a custom index.
if you make this query on you dev environment it should add it to the index.yaml and after redeploying your app it get's build and you can make this query online too. On Nov 7, 2010, at 2:13 AM, ZS wrote: > I have a query like > a=x AND a=y AND b=z AND c=t > and it is failing saying there is no suitable index. I thought all > equalities is always allowed? Does that not apply if there are two > equalities on the same property? Yet a=x AND a=y AND b=z works ok so > what is the rule? > > Thanks > > -- > 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.
