diff options
| author | Anton Danilchenko <anton.danilchenko@gmail.com> | 2012-11-18 18:46:39 +0200 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2012-11-19 18:46:36 -0500 |
| commit | 5b6db35a7472d745c2878b77406c0b730ea362d7 (patch) | |
| tree | 6b16a75411f056887dd6b5dafad96a67602e6f6a /docs | |
| parent | 27ecabf73f82104dd7624a9321ea34b15e51d83d (diff) | |
[1.5.X] Fixed typo in docs/ref/models/querysets.txt
Backport of 76859e6eab from master
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. |