Fixed #11278 -- Clarified query documentation regarding bulk assignment of m2m values. Thanks to zgoda for the patch.
git-svn-id: http://code.djangoproject.com/svn/django/trunk@11045 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
parent
457a1f9a03
commit
3db96017ba
|
@ -945,11 +945,17 @@ in the :ref:`related objects reference <ref-models-relations>`.
|
||||||
Removes all objects from the related object set.
|
Removes all objects from the related object set.
|
||||||
|
|
||||||
To assign the members of a related set in one fell swoop, just assign to it
|
To assign the members of a related set in one fell swoop, just assign to it
|
||||||
from any iterable object. Example::
|
from any iterable object. The iterable can contain object instances, or just
|
||||||
|
a list of primary key values. For Example::
|
||||||
|
|
||||||
|
Example::
|
||||||
|
|
||||||
b = Blog.objects.get(id=1)
|
b = Blog.objects.get(id=1)
|
||||||
b.entry_set = [e1, e2]
|
b.entry_set = [e1, e2]
|
||||||
|
|
||||||
|
In this example, ``e1`` and ``e2`` can be full Entry instances, or integer
|
||||||
|
values representing primary keys.
|
||||||
|
|
||||||
If the ``clear()`` method is available, any pre-existing objects will be
|
If the ``clear()`` method is available, any pre-existing objects will be
|
||||||
removed from the ``entry_set`` before all objects in the iterable (in this
|
removed from the ``entry_set`` before all objects in the iterable (in this
|
||||||
case, a list) are added to the set. If the ``clear()`` method is *not*
|
case, a list) are added to the set. If the ``clear()`` method is *not*
|
||||||
|
|
Loading…
Reference in New Issue