Hi Arny, The reason the offset works this way is related to bigtable and the way the datastore has been implemented on top of it. If what you need is paging, e.g., scrolling through a dataset of search results, there are more efficient ways of doing this than using the offset. Some of them are discussed here:
http://code.google.com/appengine/articles/paging.html http://www.youtube.com/watch?v=Oh9_t5W6MTE Eric On Apr 14, 11:33 am, Wooble <geoffsp...@gmail.com> wrote: > You can use offset and limit perfectly well to deal with fewer than > 1000 results. If your queries would return more results, of course > they're not very useful since the datastore won't return more then > 1000 results under any circumstances. > > On Apr 14, 12:44 pm,Arny<arny...@googlemail.com> wrote: > > > Hi, > > > Any of the Gurus can explain why do google serve us with the OFFSET & > > LIMIT while you can't even use it? > > > Tried it inside the Data Viewer and getting the following results: > > LIMIT <= 1000 : ok > > LIMIT > 1000 : failure > > OFFSET < 1000 : ok > > OFFSET < ~2800 : works partially > > OFFSET > ~2800 : timeout.. > > > How are we suppose to do dynamic results with different ORDER types > > and ability to browse them by pages? > > --~--~---------~--~----~------------~-------~--~----~ 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-appengine@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 -~----------~----~----~----~------~----~------~--~---
