diff options
| author | Ryan Cheley <9857779+ryancheley@users.noreply.github.com> | 2022-10-21 08:02:39 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-10-21 16:02:39 +0100 |
| commit | 38936f6a0cecfdfbfc30009a1f0a725b770f0854 (patch) | |
| tree | ad4082951dacb255d380b501621db412a32ad15c /docs | |
| parent | 3e928de8add92a5f38a562abd7560b023d24b6af (diff) | |
Fixed typo in docs/ref/models/querysets.txt.
Diffstat (limited to 'docs')
| -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 223bb452b0..58d9771cc5 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 |