Ticket #13035: 13035_managers_docs_patch.diff

File 13035_managers_docs_patch.diff, 1.1 KB (added by gabrielhurley, 5 years ago)

Fixes some outdated information about default managers and contrib.admin

  • docs/topics/db/managers.txt

     
    169169
    170170If you use custom ``Manager`` objects, take note that the first
    171171``Manager`` Django encounters (in the order in which they're defined
    172 in the model) has a special status. Django interprets this first
     172in the model) has a special status. Django interprets the first
    173173``Manager`` defined in a class as the "default" ``Manager``, and
    174 several parts of Django (though not the admin application) will use
    175 that ``Manager`` exclusively for that model. As a result, it's often a
    176 good idea to be careful in your choice of default manager, in order to
    177 avoid a situation where overriding of ``get_query_set()`` results in
     174several parts of Django will use
     175that ``Manager`` exclusively for that model. As a result, it's a
     176good idea to be careful in your choice of default manager in order to
     177avoid a situation where overriding ``get_query_set()`` results in
    178178an inability to retrieve objects you'd like to work with.
    179179
    180180.. _managers-for-related-objects:
Back to Top