Cursors are nice, but not necessarily useful in all situations. I have code that uses both offsets and cursors in the same application, because I need the flexibility of offsets occasionally. In the cases where cursors can be used, I use cursors for speed. The GAE documentation comments on the limits to cursor queries here: https://developers.google.com/appengine/docs/java/datastore/queries#Limitations_of_Cursors
In particular, cursor queries do not update themselves if a new entity matching the query is added between cursor operations, or if an existing entity is updated to no longer fit the cursor query (which is a big problem if your data changes quickly, as mine does). Perhaps you could share examples of your code/datasets, and we could find ways to speed it up/reduce its costs? -Vinny P On Monday, October 8, 2012 6:09:27 PM UTC-5, James Gilliam wrote: > > So, give me an example of how it is anything but > mathematically pathological. > > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/uLV-3EW_4Z4J. 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.
