innov
/
django1
1
0
Fork 0
Code Issues Pull Requests 1 Projects Releases Wiki Activity

[1.5.X] Documented behavior of get_or_create when multiple objects are returned. 

Thanks Matt Lauber for the patch.

Backport of 71a3162a70 from master
This commit is contained in:
Tim Graham 2012-11-22 10:36:18 -05:00
parent 63546533c1
commit 84dc6afac7
1 changed files with 6 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
docs/ref/models/querysets.txt
View File

@ -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])