[google-appengine] Re: Efficient paging using __key__ instead of a dedicated unique property

2009-03-17 Thread Simo Salminen
Hi. Just for the curiosity, I did a simple pagination algo which supports 'previous' button. This is not as fancy as rodrigos, because this is not generalized for all types of queries. Also it is bit repetitive because I wanted to keep it easy to understand. Here is the code:

[google-appengine] Re: Efficient paging using __key__ instead of a dedicated unique property

2009-01-30 Thread Rodrigo Moraes
hey there, just an update: a working version of the query class with built in pagination is available at: http://bitbucket.org/moraes/appengine/src/tip/bookmark.py let me know what you think. -- rodrigo --~--~-~--~~~---~--~~ You received this message

[google-appengine] Re: Efficient paging using __key__ instead of a dedicated unique property

2008-12-17 Thread ryan
On Dec 16, 10:33 pm, Thomas Johansson prenc...@gmail.com wrote: One question springs to mind, however: What about user friendly / readable / hackable urls? How would you go about implementing e.g. ? page=10 or ?offset=42 with the entity bookmarks, in a way that doesn't require a bunch of

[google-appengine] Re: Efficient paging using __key__ instead of a dedicated unique property

2008-12-17 Thread Rodrigo Moraes
On Wed, Dec 17, 2008 at 4:33 AM, Thomas Johansson wrote: ryan: We really *really* need some kind of pagination built-in though, it has to be said. It is more or less the number one constraint for everybody I've talked to, and something we all need in one way or another. The other constraints

[google-appengine] Re: Efficient paging using __key__ instead of a dedicated unique property

2008-12-16 Thread Thomas Johansson
Has anybody taken on the challenge of implementing a library for this? I'd love to see one, but it's too big a task for me to tackle currently. One question springs to mind, however: What about user friendly / readable / hackable urls? How would you go about implementing e.g. ? page=10 or

[google-appengine] Re: Efficient paging using __key__ instead of a dedicated unique property

2008-12-12 Thread ryan
ugh. i don't know why i thought the long lines in the examples table would survive. i've uploaded the post as a text file, with the long lines intact: http://groups.google.com/group/google-appengine/web/efficient_paging_using_key_instead_of_a_dedicated_unique_property.txt

[google-appengine] Re: Efficient paging using __key__ instead of a dedicated unique property

2008-12-12 Thread Alexander Kojevnikov
Still, we've come up with some interesting ideas, and I'd like to share one of them here. Brilliant, thanks Ryan! Is there a chance that this will be integrated into the Datastore Viewer? --~--~-~--~~~---~--~~ You received this message because you are

[google-appengine] Re: Efficient paging using __key__ instead of a dedicated unique property

2008-12-12 Thread ryan
On Dec 12, 5:18 pm, Alexander Kojevnikov alexan...@kojevnikov.com wrote: Is there a chance that this will be integrated into the Datastore Viewer? unfortunately, no, that's unlikely. if/when we do implement efficient paging, we'll probably use something else. this is nontrivial to implement,