Ticket #12579: 12579.diff

querysets.txt

@@ -1336 +1336 @@
 created and the key already exists in the database, an
 :exc:`~django.db.IntegrityError` will be raised.
 
+The ``get_or_create()`` method is not atomic.So if unique/unique together is not
+implemented on fields used in :meth:`get()` call at database level,
+concurrent calls to ``get_or_create()`` method end up creating duplicate objects in database.
+If a unique/unique together is implemented, multiple threads can get to the point of save() where
+one thread successfully creates the object while the others raise :exc:`~django.db.IntegrityError`. 
+
 Finally, a word on using ``get_or_create()`` in Django views. As mentioned
 earlier, ``get_or_create()`` is mostly useful in scripts that need to parse
 data and create new records if existing ones aren't available. But if you need