Interesting. That seems kinda tedious. So suppose someone were to write a wrapper around the datastore get API that handled the 1000 entity limit by automatically splitting queries into 1k groups, but returned them seamlessly to the user as if they were one query. Would that be a violation of the appengine TOS? Would users of such a wrapper risk having their app shut off?
On Sep 15, 12:48 am, 风笑雪 <kea...@gmail.com> wrote: > You can sort the entities by __key__, and get the first 1000 entities. > Then add a filter for __key__ that bigger(or smaller) than the 1000th > entity, to get 1001st to 2000th entities, and so on. > > 2009/9/15 Locke <locke2...@gmail.com>: > > > > > From the documentation: "maximum number of entities in a batch get: > > 1000" > > > Does this mean that if I have say 5000 accounts which I am keeping > > track of in the datastore, and I do a query to list all of them, it > > would not work? I would have to do five queries in a row, hard coding > > distinct queries to get account numbers 0-999, 1000-1999, 2000-2999, > > 3000-3999, and 4000-4999? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
