Hi Ryan, So I guess what you're saying here is that a put() is not atomic with respect to all indices. I will keep that in mind for sure, but it's unfortunate - adds a lot of code if you have to check all the time to actually see if an index is correct!
Ben On Apr 16, 9:08 am, ryan <ryanb+appeng...@google.com> wrote: > the discussion here is pretty on target. thanks, all! > > beyond the points already raised, i'd guess this is caused either by > writes (puts or deletes) that returned errors, and therefore didn't > update all indices, or an index consistency bug that we're currently > working on: > > http://code.google.com/p/googleappengine/issues/detail?id=901 > > in both cases, a successful put() on the entity in question will fix > the problem. we're still working on issue 901, and we definitely > expect to have that resolved soon. as for put() and delete() calls > that return errors (like timeouts), we're always working to reduce > those, but they'll unfortunately always be possible, so you'll want to > plan for that. --~--~---------~--~----~------------~-------~--~----~ 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 google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
