Opened 8 years ago
Last modified 8 years ago
#26429 closed Bug
Name clash of merge migrations after squashing — at Initial Version
| Reported by: | xgenadam | Owned by: | nobody |
|---|---|---|---|
| Component: | Migrations | Version: | 1.9 |
| Severity: | Normal | Keywords: | makemigrations merge clash |
| Cc: | Triage Stage: | Accepted | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
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.
Note:
See TracTickets
for help on using tickets.