diff options
author | Tim Graham <timograham@gmail.com> | 2016-04-08 11:43:02 -0400 |
---|---|---|
committer | Tim Graham <timograham@gmail.com> | 2016-04-08 11:43:38 -0400 |
commit | 1ef5a328e3b292c9809657020db080b623c3bf0f (patch) | |
tree | b10a81bb16f9efec8c51836ea4f31a0bff04d37b | |
parent | 92d77f31606e5fb2b1a5d0963fed0433d766a920 (diff) | |
download | django-1ef5a328e3b292c9809657020db080b623c3bf0f.tar.gz |
[1.9.x] Refs #22268 -- Fixed typo in docs/ref/models/querysets.txt
Backport of 5ac7c8f7ab2b2e1fec50abb14539a2eb520d1995 from master
-rw-r--r-- | docs/ref/models/querysets.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/ref/models/querysets.txt b/docs/ref/models/querysets.txt index 6ea5390dff..b215cae761 100644 --- a/docs/ref/models/querysets.txt +++ b/docs/ref/models/querysets.txt @@ -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 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 -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 :class:`~django.db.models.ManyToManyField`:: |