Thanks for the reply. Well there is either a bug in the system or the documentation because the docs do not mention this as far as I can tell. Inconsistencies like this could produce major errors in my application and I would consider that a huge defect regardless of whether it is documented. As I've only seen it once, I'll hope it doesn't happen again...
Thanks, Larry On Nov 27, 9:53 pm, Duncan <[EMAIL PROTECTED]> wrote: > On Nov 27, 6:31 pm, Larry <[EMAIL PROTECTED]> wrote:> Scanning the relevant > datastore API docs hasn't yielded any insight > > into what is going on! It seems quite like to me that this is a bug on > > Google's side rather than in my code. > > 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. > > So not a bug on Google's side, rather a fundamental restriction of the > system that you hadn't fully realised. --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
