I've implemented routines to handle contention at a large level, a custom pipeline implementation, there also also basic checks to prevent overwriting an entity.
However there are some operations that require no overwrite to occur, for example: - Signup related updates, email, external_user_id etc - Email verification - User information updates When these get overwritten by another update simultaneously, it creates a really disturbing experience I've done a lot to prevent these, yet they do still happen rarely, and by rarely it seems >1%, a lot My plan is to dive into more custom routines to implement "make sure" routines / prevention routines I'm wondering whether there is something really basic I'm missing that achieves what I want to do For example I've never used transactions, without actually using it, learning from the use cases, the documentation of transactions were meaningless to me I would appreciate any advice (I'm also extremely unlucky, or lucky, tested my new app with ~10 users, all of them experienced unique problems, some issues that occurred probably have <1/10000 probability of occurrence, a user triggered a second signup request, probably by page refresh, it would only cause an issue if the last part of the routine would execute around the same millisecond, and it did) -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/groups/opt_out.
