Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Browse files

Documented behavior of get_or_create when multiple objects are returned.

Thanks Matt Lauber for the patch.
  • Loading branch information...
commit 71a3162a70a282f150f76e8f0fc5865aa7a338a4 1 parent 9e11253
@timgraham timgraham authored
Showing with 6 additions and 4 deletions.
  1. +6 −4 docs/ref/models/querysets.txt
View
10 docs/ref/models/querysets.txt
@@ -1321,10 +1321,12 @@ The above example can be rewritten using ``get_or_create()`` like so::
Any keyword arguments passed to ``get_or_create()`` — *except* an optional one
called ``defaults`` — will be used in a :meth:`get()` call. If an object is
-found, ``get_or_create()`` returns a tuple of that object and ``False``. If an
-object is *not* found, ``get_or_create()`` will instantiate and save a new
-object, returning a tuple of the new object and ``True``. The new object will
-be created roughly according to this algorithm::
+found, ``get_or_create()`` returns a tuple of that object and ``False``. If
+multiple objects are found, ``get_or_create`` raises
+:exc:`~django.core.exceptions.MultipleObjectsReturned`. If an object is *not*
+found, ``get_or_create()`` will instantiate and save a new object, returning a
+tuple of the new object and ``True``. The new object will be created roughly
+according to this algorithm::
defaults = kwargs.pop('defaults', {})
params = dict([(k, v) for k, v in kwargs.items() if '__' not in k])
Please sign in to comment.
Something went wrong with that request. Please try again.