I know this is a classical problem, but I still don’t know how to do it. On Google App Engine, I have a member registration form which uses jQuery’s validation to check if a username exists.
There of course is a concurrency problem: several users try to register, enter the same username, Validation finds the username available, and allow them to press “Add” at the approximately same time. Validation wouldn’t detect this. In my application, username, email, and Personal ID should all be unique. How do I prevent the following code from having the concurrency problem:
member = Member()
member.username = self.request.get('username')
member.Pid = self.request.get('Pid')
member.email = self.request.get('email')
...
As the uniqueness constraint is on username, you have to use it as key in datastore and use transactions.
This makes sure only one person can register a username.
The jQuery helper would check if
ndb.Key(Member, userid).get()gives a result or not. The GET is not transactional.To improve usability client side in “reserving” a username after checking availability, you could use memcached as suggested by Daniel, but I’d call YAGNI, skip the complexity and rather let some people get validation error after submitting the form. Note that memcached is best effort and has no guarantees about anything.
If you need guaranteed uniqueness on multiple fields, you have to add Model classes for them and check in a cross group (XG) transaction.