From d3404c1ca8fab9dcde84b2eab29863eae11954ce Mon Sep 17 00:00:00 2001 From: Josh Schneier Date: Wed, 4 Feb 2015 01:01:59 -0500 Subject: [PATCH] [1.7.x] Fixed typos of "select_related" in docs. Backport of 7d363ed43247a80d2b764723e1bf6e0e6da4e82f from master --- docs/ref/models/querysets.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/ref/models/querysets.txt b/docs/ref/models/querysets.txt index 6d12389d49..612402461b 100644 --- a/docs/ref/models/querysets.txt +++ b/docs/ref/models/querysets.txt @@ -771,8 +771,8 @@ You can use ``select_related()`` with any queryset of objects:: The order of ``filter()`` and ``select_related()`` chaining isn't important. These querysets are equivalent:: - Entry.objects.filter(pub_date__gt=timezone.now()).selected_related('blog') - Entry.objects.selected_related('blog').filter(pub_date__gt=timezone.now()) + Entry.objects.filter(pub_date__gt=timezone.now()).select_related('blog') + Entry.objects.select_related('blog').filter(pub_date__gt=timezone.now()) You can follow foreign keys in a similar way to querying them. If you have the following models::