Opened 14 years ago

Closed 14 years ago

#2892 closed defect (duplicate)

custom manager not used by contrib.Admin

Reported by: davidschein@… Owned by: Adrian Holovaty
Component: contrib.admin Version:
Severity: normal Keywords:
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no


It seems that the Django *is not* interpretting the first Manager defined in a class as the "default" Manager.

It always uses an instance of the models.Manager unless you explicitly put a manager field in your Admin class, as in:

    class Admin:
        manager = CourseManager()

I think #2644 is related or the same.
The patch, #2870, obviously won't work unless this behavior works.

Change History (1)

comment:1 Changed 14 years ago by Lakin Wecker <lakin@…>

Resolution: duplicate
Status: newclosed

I'm certain that #2644 is a duplicate, and it was reported first, so I'm marking this one as a duplicate. I've linked this bug to the other one so that your comments aren't lost. :)

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