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:02 -0400 |
| commit | 5ac7c8f7ab2b2e1fec50abb14539a2eb520d1995 (patch) | |
| tree | 0c4b0463b5143bf22a825e27fa2eac2ed81c071c /docs | |
| parent | 92053acbb9160862c3e743a99ed8ccff8d4f8fd6 (diff) | |
Refs #22268 -- Fixed typo in docs/ref/models/querysets.txt
Diffstat (limited to 'docs')
| -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 ef0bd221e1..f8a2f10f7c 100644 --- a/docs/ref/models/querysets.txt +++ b/docs/ref/models/querysets.txt @@ -641,7 +641,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`:: |
