#26881: Crash when creating migrations with managers having
use_in_migrations=True
-------------------------------------+-------------------------------------
Reporter: claudep | Owner: nobody
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
-------------------------------------+-------------------------------------
Comment (by Loïc Bistuer <loic.bistuer@…>):
In [changeset:"a2af2420ce8f4f2bf67e095740e62fa2d3c249cf" a2af242]:
{{{
#!CommitTicketReference repository=""
revision="a2af2420ce8f4f2bf67e095740e62fa2d3c249cf"
[1.10.x] Fixed #26881 -- Fixed duplicate managers in migrations.
When both parent and child models had managers with the same name and
a migrations opt-in both were added to the migration state.
Backport of dab83e5ba108c08a04ae400ac5354fd73e26c6f5 from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/26881#comment:6>
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/065.c9c7798a666a82140d10498324ac4952%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
