From 5ac7c8f7ab2b2e1fec50abb14539a2eb520d1995 Mon Sep 17 00:00:00 2001 From: Tim Graham Date: Fri, 8 Apr 2016 11:43:02 -0400 Subject: [PATCH] Refs #22268 -- Fixed typo in docs/ref/models/querysets.txt --- docs/ref/models/querysets.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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`::