There is no cache of query results when you use cursors - or limit/offset. They're just pointers into the real datastore index. If you change the datastore, the results will change.
If you want 100% guaranteed unchanging query results in a highly dynamic dataset, cache the results yourself in the memcache. Or send them all to the client and page with javascript. Jeff On Sun, Feb 27, 2011 at 5:43 AM, Luke <[email protected]> wrote: > let say we use cursor and we fast-forward page. > > 1-10 > 11-20 when reached here, one record in 23 is deleted > 21-30 > > on in this case, when cursor is at 21, it will only show 9 record on > this page correct? > > > In other words, we cannot use global count (total records) for paging > unless we will have to start from page 1 again (1-10) again ? > > > -- > 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. > > -- 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.
