summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJosh Schneier <josh.schneier@gmail.com>2015-02-04 01:01:59 -0500
committerTim Graham <timograham@gmail.com>2015-02-04 07:33:48 -0500
commitd3404c1ca8fab9dcde84b2eab29863eae11954ce (patch)
tree84091250bd54f02905c7f4099ae763edbbe65f4c
parent2401ef8682220cf49fcc053fe8c933fd9b8275fe (diff)
[1.7.x] Fixed typos of "select_related" in docs.
Backport of 7d363ed43247a80d2b764723e1bf6e0e6da4e82f from master
-rw-r--r--docs/ref/models/querysets.txt4
1 files 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::