This isn't a bad solution, but it has several problems: - It doesn't scale - Cache could have holes. I guess then you could grab a query and scroll though the first 20 pages to fill out the cache. You could actually start at the highest cursor before the requested page and page forward to fill out any gapes in the cache. - What happens when the data changes. Say some one adds a full page of elements in the middle then the cache would miss these results when scrolling back
I am planning to implement a new type of "Plannable" cursor that will be smaller and allow for backwards scrolling. It will however require an extra index for every index you want to page over. It is roughly identical to John's suggestion, so in the mean time I would recommend that (just remember to include __key__ desc in the descending index). On Apr 23, 4:02 pm, boustanihani <[email protected]> wrote: > To achieve this I am saving all corsors (in an ArrayList<String>) on > the Client and reusing them for getting bachward pages :) ... this > works! What do u think? > > On 2 Apr., 21:57, Arny <[email protected]> wrote: > > > Hi, > > > Is there a way to get acursorto pagebackto a previous page? > > If not, whats the point of paging forward only? I'm not building an > > ajax page. > > > Regards > > -- > 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 > athttp://groups.google.com/group/google-appengine-java?hl=en. -- 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.
