The query restrictions are an artifact of the way App Engine's datastore is constructed, which makes certain operations (e.g. queries and reads) very fast and scalable but does limit the types of queries you can make, though you can typically get around these restrictions by re-thinking your model a bit.
We are working on adding built-in cursor support for easier paging through entities and have just added a datastore statistics API for, among other things, getting the total entity count, even if it exceeds 1,000. More details here: http://code.google.com/appengine/docs/java/datastore/stats.html And we also have a data export utility included with the SDK to make it easier for you to back up or even move off of App Engine should you choose to, and we're continuing to look at ways of making App Engine, particularly the datastore component, easier to use. http://code.google.com/appengine/docs/python/tools/uploadingdata.html#Downloading_Data_from_App_Engine - Jason On Mon, Oct 19, 2009 at 1:53 PM, vetch <[email protected]> wrote: > > On 6 Paź, 10:03, "Jason (Google)" <[email protected]> wrote: > > * Because App Engine queries can only return up to 1,000 results, > > count(this) will never return above 1,000, even if you have more than > 1,000 > > entities, so bear this in mind. > > I'm deeply shocked. This works like some black hole. > > You put your data there simply, but can't get them back that simply. > > In connection with restricions (inequality property filter), it is > even harder to get anything more complex. > > BiGAppEngine disappointment. > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine for Java" 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-java?hl=en -~----------~----~----~----~------~----~------~--~---
