The 1000 result limit was removed in Feb when they added query cursors [1]. You can use the task queue to perform fault tolerant map reduce jobs [2]. Full text search should be announced this month at GoogleIO.
[1] http://googleappengine.blogspot.com/2010/02/app-engine-sdk-131-including-major.html [2] http://code.google.com/appengine/articles/deferred.html Robin On May 6, 12:27 pm, mdipierro <[email protected]> wrote: > What it really needs in my view is > > 1) remove the limit of 1000 records/select > 2) provide real full text search (what users expect when they think of > google and the one thing that they do not provide. You can do it with > hacks but I do not believe it scales) > 3) real transactions > > On May 6, 11:56 am, waTR <[email protected]> wrote: > > > > > GAE is useless without being able to use MapReduce...without MapReduce > > you cannot do any relationships with tables of any significant size. > > > I get this opinion from ex-googlers. > > > On May 6, 7:47 am, mdipierro <[email protected]> wrote: > > > > My experience is that GAE is fine if you need to store many chunks of > > > data (like wiki page) with very little relations to each other (no > > > complex references), retrieve them by key/id (no complex queries) and > > > are planning to have a lot of concurrent requests/second for that > > > data. > > > > GAE is slow but it scales. It scales as long as queries are simple. > > > You lose the ability to manipulate server-side an arbitrary large > > > number of records. You can only fetch 1000 records at the time. You > > > also risk data integrity because you have only single entity > > > transactions not real transactions as in a relational database. > > > > I use it and I like it but for web2py.com for example, with 50000 > > > requests/day I prefer to pay $20/month and run on a VPS. > > > > Massimo > > > > On May 6, 9:08 am, mike <[email protected]> wrote: > > > > > From my past experiences i have found GAE a little slow, is this just > > > > me? With web2py development what has the community found with > > > > deploying to GAE.
