diff options
| author | Tim Graham <timograham@gmail.com> | 2012-11-19 15:45:53 -0800 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2012-11-19 15:45:53 -0800 |
| commit | 8b659e439b51953064a7a79924b4066e08d7127d (patch) | |
| tree | cbfa8f6918af19d447ab74451fa9b69ebe97d663 /docs | |
| parent | c559c3c3b9fb99c723a9e0d060ecebc805a6eb30 (diff) | |
| parent | 76859e6eab1e411d1b7cc92d8160e89df6375cfb (diff) | |
Merge pull request #536 from 1st/patch-1
Fixed typo in docs/ref/models/querysets.txt
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. |