Opened 10 years ago

Closed 10 years ago

Last modified 8 years ago

#11286 closed (fixed)

Dumpdata management command does not use _default_manager

Reported by: Marc Remolt Owned by: nobody
Component: Core (Other) Version: master
Severity: Keywords:
Cc: Triage Stage: Accepted
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no


In django/core/management/commands/ on line 75f:

for model in model_list:

As I understand it, Django core now exclusively uses model_default_manager instead of the hard coded model.objects, so there is no reason to keep is here.

Change History (3)

comment:1 Changed 10 years ago by Karen Tracey

Triage Stage: UnreviewedAccepted

This does seem to be an inadvertent regression of an earlier fix, as noted here:

comment:2 Changed 10 years ago by Russell Keith-Magee

Resolution: fixed
Status: newclosed

(In [10967]) Fixed #11286 -- Ensured that dumpdata uses the default manager, rather than always using the manager called objects. Thanks to Marc Remolt for the report.

comment:3 Changed 8 years ago by Jacob

milestone: 1.1

Milestone 1.1 deleted

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