#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 | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
----------------------------+--------------------
Working on a project with Models written with migrations generated by
Django 1.8 (upgraded to 1.9), when running `makemigrations`, some
unexpected migrations were generated.
{{{#!python
...
migrations.AlterModelManagers(
name='some_model',
managers=[
('objects', django.db.models.manager.Manager()),
],
),
}}}
We've never run `AlterModelManagers` in the past. Instead of the Manager
we define being added, the default Manager is being set.
I can add code examples + instructions later
--
Ticket URL: <https://code.djangoproject.com/ticket/26643>
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/052.ad15ab5d1c17043f870aa8a547615405%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
