Comment 1 for bug 894105

This sounds like a problem with the database schema for U1's installation of django-openid-auth. The database schema should have a unique constraint on UserOpenID.claimed_id, so this particular error should never have occurred.

It does leave open the question about how duplicate claimed_id values got into the database in the first place: the code paths that create UserOpenID records only do so after checking that there are no other records with the given claimed_id value, so I would only expect to see this in a race condition in a new user logging in twice at the same time. The constraint is designed to cause that code path to fail rather than corrupt the database.