mirrors/django
1
0
Fork 0
mirror of https://github.com/django/django.git synced 2025-07-19 17:19:12 +00:00
Code Issues 32 Releases Wiki Activity

[1.9.x] Refs #22268 -- Fixed typo in docs/ref/models/querysets.txt

Browse Source 
Backport of 5ac7c8f7ab2b2e1fec50abb14539a2eb520d1995 from master
This commit is contained in:
Tim Graham 2016-04-08 11:43:02 -04:00
parent 92d77f3160
commit 1ef5a328e3
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -651,7 +651,7 @@ achieve that, use ``values_list()`` followed by a ``get()`` call::
specific use case: retrieving a subset of data without the overhead of creating specific use case: retrieving a subset of data without the overhead of creating
a model instance. This metaphor falls apart when dealing with many-to-many and a model instance. This metaphor falls apart when dealing with many-to-many and
other multivalued relations (such as the one-to-many relation of a reverse other multivalued relations (such as the one-to-many relation of a reverse
foreign key) because the the "one row, one object" assumption doesn't hold. foreign key) because the "one row, one object" assumption doesn't hold.
For example, notice the behavior when querying across a For example, notice the behavior when querying across a
:class:`~django.db.models.ManyToManyField`:: :class:`~django.db.models.ManyToManyField`::