diff options
| author | dbogar89 <162604156+dbogar89@users.noreply.github.com> | 2025-04-27 07:40:14 +0100 |
|---|---|---|
| committer | Mariusz Felisiak <felisiak.mariusz@gmail.com> | 2025-04-27 08:40:41 +0200 |
| commit | c08764cb2e047b20728661ce8c17d0fca498b2cd (patch) | |
| tree | 4d1063f5c7b62948ee8303f81be04d68ebd71a09 | |
| parent | 90fa9f4cc090d07bc59717120cc1a5a3a84e1acb (diff) | |
[5.2.x] Fixed #36335 -- Fixed typo in docs/topics/db/managers.txt.
Backport of 7b394b9988b986429a4da4e60416e0f08ff649e5 from main
| -rw-r--r-- | docs/topics/db/managers.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/topics/db/managers.txt b/docs/topics/db/managers.txt index 3a7a635e49..1cd3ba962f 100644 --- a/docs/topics/db/managers.txt +++ b/docs/topics/db/managers.txt @@ -197,7 +197,7 @@ Using managers for related object access ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ By default, Django uses an instance of the ``Model._base_manager`` manager -class when accessing related objects (i.e. ``choice.question``), not the +class when accessing related objects (e.g. ``choice.question``), not the ``_default_manager`` on the related object. This is because Django needs to be able to retrieve the related object, even if it would otherwise be filtered out (and hence be inaccessible) by the default manager. |