Ticket #8419: fix_get_or_create_race.v2.diff

django/db/models/query.py

@@ -328 +328 @@
                 params.update(defaults)
                 obj = self.model(**params)
                 sid = transaction.savepoint()
-                obj.save()
+                obj.save(force_insert=True)
                 transaction.savepoint_commit(sid)
                 return obj, True
             except IntegrityError, e:

docs/ref/models/querysets.txt

@@ -577 +577 @@
         obj = Person.objects.get(first_name='John', last_name='Lennon')
     except Person.DoesNotExist:
         obj = Person(first_name='John', last_name='Lennon', birthday=date(1940, 10, 9))
-        obj.save()
+        obj.save(force_insert=True)
 
 This pattern gets quite unwieldy as the number of fields in a model goes up.
 The above example can be rewritten using ``get_or_create()`` like so::
@@ -596 +596 @@
     params = dict([(k, v) for k, v in kwargs.items() if '__' not in k])
     params.update(defaults)
     obj = self.model(**params)
-    obj.save()
+    obj.save(force_insert=True)
 
 In English, that means start with any non-``'defaults'`` keyword argument that
 doesn't contain a double underscore (which would indicate a non-exact lookup).