#25044 closed Bug (fixed)
Renaming a ManyToManyField's through table creates a broken migration
Reported by: | Ian Foote | Owned by: | Vytis Banaitis |
---|---|---|---|
Component: | Migrations | Version: | dev |
Severity: | Normal | Keywords: | |
Cc: | Triage Stage: | Ready for checkin | |
Has patch: | yes | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
I've created a minimal example demonstating the broken migration at https://github.com/Ian-Foote/django-bug-sandbox/pull/1.
Change History (13)
comment:1 by , 9 years ago
Component: | Uncategorized → Migrations |
---|---|
Type: | Uncategorized → Bug |
comment:2 by , 9 years ago
Triage Stage: | Unreviewed → Accepted |
---|
comment:3 by , 9 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:4 by , 9 years ago
Owner: | changed from | to
---|
comment:5 by , 9 years ago
Owner: | removed |
---|---|
Status: | assigned → new |
Releasing the ticket since I haven't been able to find time to look at it.
comment:7 by , 9 years ago
Has patch: | set |
---|---|
Owner: | set to |
Status: | new → assigned |
comment:9 by , 9 years ago
Patch needs improvement: | unset |
---|
I have created a new PR, in which I've updated RenameModel
operation to deal with M2M through
.
comment:11 by , 8 years ago
Triage Stage: | Accepted → Ready for checkin |
---|
Note:
See TracTickets
for help on using tickets.
I'd like to take a stab at it for a couple of days.