Given the following two queries and their composite index requirements: Query A: SELECT WHERE propA == param1 ORDER BY propB ASC, propC ASC
coposite index required: 1. propA asc, 2. propB asc, 3. propC asc Query B: SELECT WHERE propA == param1 && propB == param2 && propC > param3 ORDER BY propC ASC coposite index required: 1. propB asc, 2. propA asc, 3. propC asc Question 1: Is it a bug that the Query B reverses the index order of the first two equality filters? Question 2: Is it somehow possible to make Query B _reuse_ the composite index defined for Query A? Question 3: Should I fill a feature request so that app engine tries to optimize queries to match existing composite indexes, if possible? Thank you, J. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine for Java" 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-java?hl=en -~----------~----~----~----~------~----~------~--~---
