Hello! I uploaded the first version of my app yesterday, and at once I had problems with db errors: the same request (add A, update a counter in B) raised an error three times in a row: A was added, but B was not updated for some reason until the fourth try.
And on the fourth try everything went smoothly and I ended up with four new A objects and only one "trace" of the operation in the counter in B. I'm 100% sure that the requests were the same, and I have never saw this error on the local machine. I can't replicate the issue today, but now my gmail account is unusually buggy. So my question: was it a one-off issue with App Engine/new upload, and I should expect it to work smoothly 99.9% of the time, or should I re- design my app in expectation of frequent server-side errors? If it is the second, how do I wrap the operation cites above (add object A, update a counter in object B) in a transaction? Transactions are a bit weak in App Engine... Thanks for you help! --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
