On Feb 2, 11:05 am, Robin B <[email protected]> wrote: > > And I assume you are saying there is no limit on # keys/models for > batch get/put/delete.
actually, we do have limits on those: 1000 keys per batch get and 500 entities/keys per batch put/delete. > What about when using cron? Will the same rules apply? without getting too much into cron itself, yes, any app engine code that uses the datastore will generally be subject to these per- operation limits. > On Feb 2, 11:44 am, Marzia Niccolai <[email protected]> wrote: > > > There is no 'maximum' for queries per request or maximum number of > > entities per request, these things rely heavily on the size and shape > > of the data you are querying. this is true. by "30 queries per request," i'm guessing robin actually meant 30 subqueries per query. this happens with the IN and != operators, which are implemented in pure python, in user land, by running multiple subqueries and merging the results. these kinds of queries are limited to at most 30 subqueries. this is mentioned in the "Note" on http://code.google.com/appengine/docs/python/datastore/gqlreference.html . we're planning to publish a more comprehensive document with all of these limits soon. thanks for the nudge! --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
