Hey Greg, Do you have any blind try-excepts in your code? If it is silently failing, I'd guess something issilently catching and ignoring the exception.
Also, as Noah mentioned, a global query immediately after a put might not get the latest results. A get-by-key or ancestor query will. Robert On Wednesday, July 6, 2011, Greg <[email protected]> wrote: > Hi - > > I've just discovered that occasionally put()s in my python HR > datastore app are failing almost silently. "Almost" because I am > seeing a "Transaction collision. Retying..." warning logged at the > time the write is supposed to happen, but nothing else - certainly no > exception is raised. > > This is severely impacting the integrity of my data. I'm currently > running a remote checking script daily to fix the data, but this is a > horrible band-aid and should not be required. Either the put() should > succeed, or an exception should be raised. > > Any ideas? > > Cheers > Greg. > > -- > 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. > > -- ------ Robert Kluin Ezox Systems, LLC -- 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.
