The entity will be update once every 5~10 seconds(when the user play a move), and every update is step by step. Their is no concurrently update and no contention. So that transaction won't work for this problem, right? besides, their is a limitation that we can not start a query in transaction, so it's hard for me to try it.
On 4月22日, 上午8时56分, Nick Rudnik <nrud...@gmail.com> wrote: > You should probably start a transaction, query for the entity, do the > update, and commit the transaction. Otherwise, you could be inadvertently > updating stale copies of the entity. If you expect many users to update the > same entity concurrently, you will probably have contention issues which can > be avoided by implementing a sharded counter. -- 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.
