> > There was a document somewhere, but I can't remember offhand exactly > > where which explains some of the aspects of how the system works. In > > particular it points out that it can take some time between the data > > being updated and the index being updated. So for your example if the > > index records the last access order as B, A, C but A has just hit the > > system you could get the sort of result you describe where a recent > > access occurs somewhere further down the list. > > That should never be the case. If the index wasn't fully updated, it > should serve you an old version of both the index and the data. If > something else happens, it is definitely a bug, so you should file a > ticket giving as much information as you can.
Dave, this behaviour is documented here (see the section called "The commit() process"): http://code.google.com/appengine/articles/transaction_isolation.html It looks like a fundamental limitation of the datastore, I doubt it's ever going to be fixed. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
