I still do not know how to do paging...I can only get the next link, but I
can not get the page 2,3,4,5,6,7,8 more link. Wish you can give me more
hint. Thanks
On Mon, Jan 26, 2009 at 7:32 AM, Marzia Niccolai ma...@google.com wrote:
Hi,
This may not work for your particular use case, but you
Well to answer your question, you'd need to regenerate your index, or
build it in such a way as items can be removed from it.
My approach to paging was this. I determined for my product I didn't
need to offer more than 100 items in a set.
When the system that needs paging is first hit, I pull
Hi,
There are a couple of reliable ways to do paging with App Engine for
arbitrarily sized data sets, both of which are discussed in this
article:
http://code.google.com/appengine/articles/paging.html
And the corresponding sample code:
Thanks for your reply.
I've just read the article today and I will have a try. For search result, I
do not know what query users give and how much result. So, I can not give a
index for an instance.
On Mon, Jan 26, 2009 at 6:54 AM, Marzia Niccolai ma...@google.com wrote:
Hi,
There are a
Hi,
This may not work for your particular use case, but you can use an
equality filter in conjunction with the key filter, so instead of
something like:
suggestions = Suggestion.all().filter('__key__ =',
bookmark).order(__key__).fetch(PAGESIZE+1)
you could do:
suggestions =
__key__ filters and sort orders are definitely useful here, and
marzia's approach will work if it fits your query. you can also use
the technique described in
http://groups.google.com/group/google-appengine/browse_thread/thread/ee5afbde20e13cde
to add paging support to any query using __key__.
