I think I saw a get_or_create race condition today from concurrent runs of our data uploader that uses the model API. Ouch. The docs have several references to the api calls being atomic - now I'm thinking get_or_create is an exception. And I'm guessing lots of other people already know this.
So, assuming it's not atomic (by default) is there a way to make it safe other than using the django middleware layer to get transactions? Like a flag... or a db schema tweak.... Thanks for any help, suggestions or witty insults. John --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
