So far, I haven't had to deal with problem of paging through more than a couple dozen items, so I'm just grabbing them all and then slicing the results to get what I need. It's ugly and doesn't scale at all, but it is all that I have been able to come up with. I'm glad that I'm not the only one being stymied by this problem.
I know that it is primarily designed to scale well, but other than that, the datastore is a giant PITA. On Nov 19, 3:26 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > I gave up and just went with paging through 1000 results and figure > people shouldn't have to go back further. That's a reality for the > application I'm working on, but not one for others I'm sure. > > Besides the "if something is deleted" problem, I also found it > problematic to try and page for things that rely on taxonomy, and > other indexed features like search results and such. > > I'm hoping one day they may just figure out a way to allow offsets to > work the way most of us expect them to in queries. > > On Nov 19, 12:08 pm, Adam <[EMAIL PROTECTED]> wrote: > > > I am wrestling with the very same problem, Abel. I don't have a good > > answer just yet. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" 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?hl=en -~----------~----~----~----~------~----~------~--~---
