Django

Code

Ticket #2892 (closed: duplicate)

Opened 2 years ago

Last modified 2 years ago

custom manager not used by contrib.Admin

Reported by: davidschein@alumni.tufts.edu Assigned to: adrian
Milestone: Component: django.contrib.admin
Version: Keywords:
Cc: Triage Stage: Unreviewed
Has patch: 0 Needs documentation: 0
Needs tests: 0 Patch needs improvement: 0

Description

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.

Attachments

Change History

10/19/06 09:27:43 changed by Lakin Wecker <lakin@evolvs.com>

  • status changed from new to closed.
  • resolution set to duplicate.

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. :)

Add/Change #2892 (custom manager not used by contrib.Admin)




Change Properties
Action