Okay, now this is very strange indeed. Armed with a fresh 50K read quota today, I adjusted my query's fetch to 10 objects each. To examine all the matching objects it had to fetch 6 times to get all ~60 objects. This operation consumed 0% of my read quota!!! While it's good news, it's also very strange and leaves me with several questions:
1) Why didn't the built-in default value of .fetch(20) work? It would have run the query only 3 times, yet it consumed 100% of my read quota. 2) Why didn't the value of .fetch(100) work? It would have run the query only once, yet it consumed 100% of my read quota. 3) Why does the value of .fetch(10) consume no discernible read quota? This seems to be very mysterious behavior, not to mention frustrating and time consuming. Can anyone shed any light on these inconsistent results? -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/dAgdSQe7vuYJ. 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.
