summaryrefslogtreecommitdiff
path: root/docs/ref
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:31:43 -0500
commit7d363ed43247a80d2b764723e1bf6e0e6da4e82f (patch)
tree9aa2e57ef525d75812d63b7e5651e6bdd5d2275e /docs/ref
parent79f27f2b61aeac763ae048416ef8a97c2b639ae8 (diff)
Fixed typos of "select_related" in docs and tests.
Diffstat (limited to 'docs/ref')
-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 c54fa6d014..df0e135e79 100644
--- a/docs/ref/models/querysets.txt
+++ b/docs/ref/models/querysets.txt
@@ -787,8 +787,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::