My WAG is that a query which returns no results will cost you 1 "minor operation" (like a key-only query or a count step).
Jeff On Mon, Nov 21, 2011 at 7:08 PM, John Tantalo <john.tant...@gmail.com>wrote: > I don't doubt you need a read in each case. My point is about *what* the > read is for, and how the quota are calculated. > > App Engine has a quota for, > > - Datastore Write Operations > - Datastore Read Operations > - Datastore Index Write Ops > > Now, I understand that the indexes may be part of the datastore, but if > index write operations are separate from datastore write operations, why > aren't the read operations also separated? Clearly they are separate > things, but it seems they are combine under one quota. > > My only question is why, and whether that makes sense. > > For instance, it should be much cheaper to check if a query has results (a > index read) than to return those results (a datastore read), so wouldn't it > make more sense to have separate quotas? > > -- > 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/-/jYkQSgzJzeEJ. > > 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. > -- I am the 20% -- 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.
