It's kind of difficult to give any meaningful information though since it is fixed now and doesn't seem to relapsed... I can explain the bug but I can't give any instructions to replicate it and so I doubt it will be of much use. Also, I think it may have been due to maintenance or something similar so may be already "fixed".
If it happens again, I will inform Google, but it wasn't too bad anyway... On Nov 28, 11:30 am, "David Symonds" <[EMAIL PROTECTED]> wrote: > On Fri, Nov 28, 2008 at 8:53 AM, Duncan <[EMAIL PROTECTED]> wrote: > > 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. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
