From 5b6db35a7472d745c2878b77406c0b730ea362d7 Mon Sep 17 00:00:00 2001 From: Anton Danilchenko Date: Sun, 18 Nov 2012 18:46:39 +0200 Subject: [PATCH] [1.5.X] Fixed typo in docs/ref/models/querysets.txt Backport of 76859e6eab from master --- 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 295c996af4..abf32c9621 100644 --- a/docs/ref/models/querysets.txt +++ b/docs/ref/models/querysets.txt @@ -678,7 +678,7 @@ have ``null=True``. Usually, using ``select_related()`` can vastly improve performance because your app can avoid many database calls. However, there are times you are only interested in specific related models, or have deeply nested sets of -relationships, and in these cases ``select_related()`` can can be optimized by +relationships, and in these cases ``select_related()`` can be optimized by explicitly passing the related field names you are interested in. Only the specified relations will be followed.