It would be nice to see benchmark result. Difference is 5 custom index rows but one for each of 5 custom index in first case and 5 custom index rows but only in one custom index in second case.
For size of storage I don't care, but currently in case of non sorted result I can achieve same result with querying 5 properties or 1 multivalued property for 5 members. When GAE team finally finish 'Next gen query' implementation, especially zigzag merge join with sort (please, please, please :D) than I would have no custom indexes (every parameter for query would be in one multivalued property) and around 500-1000 api cpu ms less work for index creation. Tnx, Matija. -- 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.
