#26429: Name clash of merge migrations after squashing
----------------------------+----------------------------------------
Reporter: xgenadam | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 1.9
Severity: Normal | Keywords: makemigrations merge clash
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
----------------------------+----------------------------------------
After squashing migrations, further development can result in a merge
migration with an identical name to a squashed migration.
This is old merge is still stored in the django_migrations table and the
new merge will not be applied.
The workaround is to rename the merge to something unique. However the
automatically generated names should not clash in the first place.
--
Ticket URL: <https://code.djangoproject.com/ticket/26429>
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/051.dcfa67fa9ceadaf9d05561f3d28f2534%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
