Someone from the GAE team please enlighten me, whether the following 2 queries can really have different requirements on the ordering of the properties in the composite index declaration required for these queries:
(JDOQL syntax) A) SELECT WHERE propA == param1 ORDER BY propB ASC, propC ASC index required: 1. propA asc, 2. propB asc, 3. propC asc B) SELECT WHERE propA == param1 && propB == param2 && propC > param3 ORDER BY propC ASC index required: 1. propB asc, 2. propA asc, 3. propC asc In the query B, the propA and propB both are equality filters -- why don't they require index declared in the same order? So query B is refusing to work with the index from query A -- at least on the Java dev server. So I'm hoping this is a bug in the query index verification code in the Java dev server. If not, then the bookmarked paging technique is not implementable without "relation indexes" or some other hack, as forward/backward sorting on a single grid column would cost 6 composite indexes. In the above examples, propC is actually the __key__, if that matters. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
