On 16 Mar 2010, at 12:25, Jeff Schnitzer wrote:
I'm puzzled by the behavior of custom indexes. I have a simple test case below, a simple equality filter on one property combined with a descending sort on another property. If I set the properties with setUnindexedProperty(), the query fails to find the result. If I set the properties with setProperty(), it does.
I also wondered why - I assume that the custom index build reads the single property indexes directly which must be more efficient than reading the Entities "table".
-- 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.
