I still have a problem (July 25th 2009) with an index returning different results. When I query using a sort property that requires an index, I get vastly fewer results than when I do an unsorted query that does not use the index.
I have deleted the index and re-built it over the past week, and I still have the same problem. It can be reproduced 100% of the time with each query that uses the index. As an example, an unsorted query returns 640 results. The same query, sorted, returns 329 results. Adding a sort order to the query shouldn't shave more than a hundred results off (it should return exactly the same number of results, but in sorted order). sf On Jun 9, 11:32 pm, Rodrigo Moraes <rodrigo.mor...@gmail.com> wrote: > On Tue, Jun 9, 2009 at 8:13 PM, wrote: > > > Just a note that all previous indexes that were broken by this bug > > should be fixed now, meaning they should be returning the expected > > results. > > Hi Jason, > Thank you very much for the quick response. All my problematic indexes > are all working fine now. > > -- rodrigo --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
