Your use of key filters and sorts sounds appropriate. On Wed, Sep 9, 2009 at 12:22 AM, Corneliu Paul Lupulet < corneliu.lupu...@gmail.com> wrote:
> Hello, > > Thank you for you answers. I would like to make a clarification, why i am > using the key "property" in a query. > > Using an order by key, I am saving the key of the last modified object as a > bookmark/cursor to know where to resume the processing from. (i also use > this for pagination according to a python article i read on app-engine site, > which suggests this) > > Is there any other way to do this at the current moment ? (i've read in the > roadmaps that you will be introducing cursors) > > Another thing: > Quote: > "A key is a complex object -- you can't query on it using a simple string > literal" > Where are you quoting from? > > I have the encoded string version of the key (same thing i would obtain > from KeyFactory.KeyToString() and i am using this string in the query. > > It appears to work correctly, because the fetched elements are returned by > "key order", different from the order i were to get from comparing the > corresponding key strings lexically. > > -- > Corneliu Paul Lupulet > > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 google-appengine-java@googlegroups.com To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en -~----------~----~----~----~------~----~------~--~---
