diff options
| author | Ryan Cheley <9857779+ryancheley@users.noreply.github.com> | 2022-10-21 08:02:39 -0700 |
|---|---|---|
| committer | Mariusz Felisiak <felisiak.mariusz@gmail.com> | 2022-10-21 16:03:14 +0100 |
| commit | d2c52fc7270d82ad6403aa5aa8ca331fc1853ea1 (patch) | |
| tree | 95a88acb6a5fcd238564c62922f1e5c64039b485 /docs/ref | |
| parent | 2389c57f5d7b98c1da1c84ad71379d0df3db8b37 (diff) | |
[4.1.x] Fixed typo in docs/ref/models/querysets.txt.
Backport of 38936f6a0cecfdfbfc30009a1f0a725b770f0854 from main
Diffstat (limited to 'docs/ref')
| -rw-r--r-- | docs/ref/models/querysets.txt | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/ref/models/querysets.txt b/docs/ref/models/querysets.txt index 641ef0dd79..f5ef5e91bf 100644 --- a/docs/ref/models/querysets.txt +++ b/docs/ref/models/querysets.txt @@ -1659,8 +1659,8 @@ one, doing so will result in an error. have measured that the difference between returning the fields you need and the full set of fields for the model will be significant. - Even if you think you are in the advanced use-case situation, **only use - ``defer()`` when you cannot, at queryset load time, determine if you will + Even if you think you are in the advanced use-case situation, **only use** + ``defer()`` **when you cannot, at queryset load time, determine if you will need the extra fields or not**. If you are frequently loading and using a particular subset of your data, the best choice you can make is to normalize your models and put the non-loaded data into a separate model |