Opened 7 years ago

Closed 7 years ago

#9476 closed (wontfix)

deprecated text in Manager's documentation

Reported by: metzeltiger Owned by: nobody
Component: Documentation Version: 1.0
Severity: Keywords:
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:

Description

The documentation at http://docs.djangoproject.com/en/dev/topics/db/managers/

"If you use custom Manager objects, take note that the first Manager
Django encounters (in the order in which they're defined in the model)
has a special status. Django interprets this first Manager defined in
a class as the "default" Manager, and several parts of Django (though
not the admin application) will use that Manager exclusively for that
model."

is wrong, the admin app is no exception to this.

Change History (1)

comment:1 Changed 7 years ago by mtredinnick

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset
  • Resolution set to wontfix
  • Status changed from new to closed

The current text is the most accurate. It's not the case that the admin will always use the default manager, since ModelAdmin.queryset() could be overridden. Assuming that (the default manager will be used) to always be the case will lead to confusion, so best that the user is warned. I don't think this is worth changing. The queryset() method should be explained in the admin documentation, but that's a separate issue.

Note: See TracTickets for help on using tickets.
Back to Top