diff options
| author | Anton Danilchenko <anton.danilchenko@gmail.com> | 2012-11-18 18:46:39 +0200 |
|---|---|---|
| committer | Anton Danilchenko <anton.danilchenko@gmail.com> | 2012-11-18 18:46:39 +0200 |
| commit | 76859e6eab1e411d1b7cc92d8160e89df6375cfb (patch) | |
| tree | 3986b52c28f14198d74b41ef47e6d96882e40424 /docs | |
| parent | 2564e310141ab0f23b5282ecaec8e820250c355a (diff) | |
Update docs/ref/models/querysets.txt
Fix typo: replace "can can" to "can"
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/ref/models/querysets.txt | 2 |
1 files changed, 1 insertions, 1 deletions
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. |