summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorTim Graham <timograham@gmail.com>2018-02-14 09:57:31 -0500
committerTim Graham <timograham@gmail.com>2018-02-15 13:17:37 -0500
commite917ea6bec45d7f789ca96a13be15df9521963e1 (patch)
tree666f1af2f215a8d67d81c7c1c749f70adc8883a0 /docs
parent7ec0fdf62afd565dd9a888300e7e33d0bf3e5fd5 (diff)
Fixed #29126 -- Doc'd the behavior of QuerySet.update_or_create() with manually specified pks.
Diffstat (limited to 'docs')
-rw-r--r--docs/ref/models/querysets.txt4
1 files changed, 4 insertions, 0 deletions
diff --git a/docs/ref/models/querysets.txt b/docs/ref/models/querysets.txt
index 2d6702beeb..72d6accd2e 100644
--- a/docs/ref/models/querysets.txt
+++ b/docs/ref/models/querysets.txt
@@ -1988,6 +1988,10 @@ As described above in :meth:`get_or_create`, this method is prone to a
race-condition which can result in multiple rows being inserted simultaneously
if uniqueness is not enforced at the database level.
+Like :meth:`get_or_create` and :meth:`create`, if you're using manually
+specified primary keys and an object needs to be created but the key already
+exists in the database, an :exc:`~django.db.IntegrityError` is raised.
+
``bulk_create()``
~~~~~~~~~~~~~~~~~