I think that get_or_create is still broken, despite this fix: 
http://code.djangoproject.com/ticket/6641

The details, along with a working solution, are in my answer here: 
http://stackoverflow.com/questions/2235318/how-do-i-deal-with-this-race-condition-in-django/2235624#2235624
I'm not sure if the solution is optimal, trying to INSERT first might be 
overally more expensive, but I think that something should be done with 
get_or_create.

Best,

Tomasz

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" 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/django-developers?hl=en.

Reply via email to