mirror of
https://github.com/django/django.git
synced 2024-12-01 15:42:04 +01:00
Removed SHOUTING in doc examples.
This commit is contained in:
parent
823af53bf6
commit
241e1e3cd7
@ -513,11 +513,9 @@ the intermediate model::
|
|||||||
Unlike normal many-to-many fields, you *can't* use ``add()``, ``create()``,
|
Unlike normal many-to-many fields, you *can't* use ``add()``, ``create()``,
|
||||||
or ``set()`` to create relationships::
|
or ``set()`` to create relationships::
|
||||||
|
|
||||||
>>> # THIS WILL NOT WORK
|
>>> # The following statements will not work
|
||||||
>>> beatles.members.add(john)
|
>>> beatles.members.add(john)
|
||||||
>>> # NEITHER WILL THIS
|
|
||||||
>>> beatles.members.create(name="George Harrison")
|
>>> beatles.members.create(name="George Harrison")
|
||||||
>>> # AND NEITHER WILL THIS
|
|
||||||
>>> beatles.members.set([john, paul, ringo, george])
|
>>> beatles.members.set([john, paul, ringo, george])
|
||||||
|
|
||||||
Why? You can't just create a relationship between a ``Person`` and a ``Group``
|
Why? You can't just create a relationship between a ``Person`` and a ``Group``
|
||||||
@ -539,7 +537,7 @@ information as to which intermediate model instance should be deleted::
|
|||||||
... invite_reason="You've been gone for a month and we miss you.")
|
... invite_reason="You've been gone for a month and we miss you.")
|
||||||
>>> beatles.members.all()
|
>>> beatles.members.all()
|
||||||
<QuerySet [<Person: Ringo Starr>, <Person: Paul McCartney>, <Person: Ringo Starr>]>
|
<QuerySet [<Person: Ringo Starr>, <Person: Paul McCartney>, <Person: Ringo Starr>]>
|
||||||
>>> # THIS WILL NOT WORK BECAUSE IT CANNOT TELL WHICH MEMBERSHIP TO REMOVE
|
>>> # This will not work because it cannot tell which membership to remove
|
||||||
>>> beatles.members.remove(ringo)
|
>>> beatles.members.remove(ringo)
|
||||||
|
|
||||||
However, the :meth:`~django.db.models.fields.related.RelatedManager.clear`
|
However, the :meth:`~django.db.models.fields.related.RelatedManager.clear`
|
||||||
|
@ -1059,7 +1059,7 @@ introduce joins when you use ``F()`` objects in an update -- you can only
|
|||||||
reference fields local to the model being updated. If you attempt to introduce
|
reference fields local to the model being updated. If you attempt to introduce
|
||||||
a join with an ``F()`` object, a ``FieldError`` will be raised::
|
a join with an ``F()`` object, a ``FieldError`` will be raised::
|
||||||
|
|
||||||
# THIS WILL RAISE A FieldError
|
# This will raise a FieldError
|
||||||
>>> Entry.objects.update(headline=F('blog__name'))
|
>>> Entry.objects.update(headline=F('blog__name'))
|
||||||
|
|
||||||
.. _topics-db-queries-related:
|
.. _topics-db-queries-related:
|
||||||
|
Loading…
Reference in New Issue
Block a user