> it still can result in timout if the data is really big How so? If you don't request "too many" items with a page query, it won't time out. You will run into runtime.DeadlineExceededErrors if you try to use too many page queries for a given request, but ....
> of no much use to most of us if we really have big data to sort and > page. You do know that the sorting for the page queries is done with the indexing and not user code, right? Query time is independent of the total amount of data and depends only on the size of the result set. (Indexing time is constant per inserted/updated entity.) On Dec 16, 12:13 am, ajaxer <calid...@gmail.com> wrote: > it is too complicated for most of us. > and it still can result in timout if the data is really big > > of no much use to most of us if we really have big data to sort and > page. > > On Dec 15, 11:35 pm, Stephen <sdea...@gmail.com> wrote: > > > > > On Dec 15, 8:04 am, ajaxer <calid...@gmail.com> wrote: > > > > also 1000 index limit makes it not possible to fetcher older data on > > > paging. > > > > for if we need an indexed page more than 10000 items, > > > it would cost us a lot of cpu time to calculate the base for GQL > > > to fetch the data with index less than 1000. > > >http://code.google.com/appengine/articles/paging.html- Hide quoted text - > > - Show quoted text - -- 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-appeng...@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.
