diff options
| author | Tim Graham <timograham@gmail.com> | 2016-06-20 09:06:41 -0400 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2016-06-20 09:07:51 -0400 |
| commit | 44eaa2dac84ed06d5179edf56224cc604d8b4879 (patch) | |
| tree | 25a9389cb229e520047c4ed4faa0fc258e579ece | |
| parent | 91d754eb2a109e5d15bdbedb3b945abc32425250 (diff) | |
[1.10.x] Fixed typo in docs/topics/db/managers.txt
Backport of 00551c3eff5cedcb9cc7ce5af97b948d62713d97 from master
| -rw-r--r-- | docs/topics/db/managers.txt | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/topics/db/managers.txt b/docs/topics/db/managers.txt index 74c93a0edc..db17354633 100644 --- a/docs/topics/db/managers.txt +++ b/docs/topics/db/managers.txt @@ -185,8 +185,8 @@ result, it's a good idea to be careful in your choice of default manager in order to avoid a situation where overriding ``get_queryset()`` results in an inability to retrieve objects you'd like to work with. -You can specify a custom default manager using :attr:`Meta.base_manager_name -<django.db.models.Options.base_manager_name>`. +You can specify a custom default manager using :attr:`Meta.default_manager_name +<django.db.models.Options.default_manager_name>`. If you're writing some code that must handle an unknown model, for example, in a third-party app that implements a generic view, use this manager (or |