[solved] The answer to this is that appengine concatenates the various properties into a single-field index (hence the one inequality filter only restriction). It looks very much as if the primary sort is on the right-most field. If no secondary sort order is requested then the remaining fields can be sorted in any way whatever. It's a curious way to do it, though I do understand the desire to trade space efficiency and write-time performance for read speed.
-- 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.
