#26643: AlterModelManagers migration is generated for all Models with custom
Managers pointing to the default Django Manager
----------------------------+--------------------------------------
Reporter: cybojenix | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------+--------------------------------------
Changes (by cybojenix):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
Further investigation shows that if you have a manager without
`use_in_migrations` set, it will explicitly set the default manager in
`AlterModelManagers` instead of the previous behaviour of not creating a
migration at all (ie, the migration treats the model as if no manager has
been set at all).
As such, I'm going to remove the bug label, however it would be good to
mention this in the release notes to avoid questions down the road.
--
Ticket URL: <https://code.djangoproject.com/ticket/26643#comment:1>
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.78893258f2ad116ff3599fc857201a10%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
