#26643: AlterModelManagers migration is generated for all Models with custom
Managers pointing to the default Django Manager
-------------------------------------+-------------------------------------
Reporter: cybojenix | Owner: schinckel
Type: Bug | Status: closed
Component: Migrations | Version: 1.10
Severity: Release blocker | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham <timograham@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"2eb7cb2fffcc382979d0731370de26b051d04659" 2eb7cb2f]:
{{{
#!CommitTicketReference repository=""
revision="2eb7cb2fffcc382979d0731370de26b051d04659"
Fixed #26643 -- Prevented unnecessary AlterModelManagers operations caused
by the manager inheritance refactor.
This also makes migrations respect the base_manager_name and
default_manager_name model options.
Thanks Anthony King and Matthew Schinckel for the initial patches.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/26643#comment:15>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.f02febad20ebffb44a560b47c2d4a201%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
