Robert, Following your post saying that there's a maximum of 30 datastore queries for any GQL query, I was a bit worried as we perform a query with an IN filter that may have an arbitrary number of values (though in general not more than about 20-30 values, depending on how the user works with the system).
What we actually do: o Java o low-level API o Query class, Query.addFilter, Query.FilterOperator.IN o the values for the IN filter are Key instances Although we do not use GQL directly, I was assuming that GQL itself only maps to the low-level API which would perform the split into underlying queries and hence be responsible for the limit. I have now performed a test with 36 values in the IN filter, which worked fine (I also made sure that it delivers actually at least one value for each Key, and I ran it online in prod GAE). So, it looks like there's not a limit of 30 in the number of values for an IN filter that is effective in our case. Also, I have not encountered such a limit in the documentation so far (I may not have dug deep enough). Can you please elaborate a bit more where exactly this limit applies (i.e. only GQL/including ll-API/only py/also java) and possibly give a pointer to the documentation? thx and best regards, Remigius. -- 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.
