diff options
| author | Mariusz Felisiak <felisiak.mariusz@gmail.com> | 2022-03-17 11:10:03 +0100 |
|---|---|---|
| committer | Mariusz Felisiak <felisiak.mariusz@gmail.com> | 2022-03-17 11:10:49 +0100 |
| commit | 1af06ffaa537fc9aefb76b6589072873d7dbf54a (patch) | |
| tree | 3b6bb3c61bf0159a3d389536e6e677f674aa71f8 /docs/ref/models | |
| parent | de5a453d51681e2f162cf3e51406ef9afc0c6863 (diff) | |
[4.0.x] Added missing backticks to function names.
Backport of 39ae8d740e30c18e46873cf82aff76588f1974c7 from main
Diffstat (limited to 'docs/ref/models')
| -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 4680cee1e6..39b53f0dc3 100644 --- a/docs/ref/models/querysets.txt +++ b/docs/ref/models/querysets.txt @@ -1618,8 +1618,8 @@ one, doing so will result in an error. 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 need - the extra fields or not**. If you are frequently loading and using a + ``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 (and database table). If the columns *must* stay in the one table for some |