#36791: Migration does not drop old M2M through-table when ManyToManyField
target
model changes
-------------------------------------+-------------------------------------
Reporter: Johanan Oppong | Owner: Johanan
Amoateng | Oppong Amoateng
Type: Bug | Status: closed
Component: Migrations | Version: 6.0
Severity: Normal | 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
-------------------------------------+-------------------------------------
Changes (by Jacob Walls <jacobtylerwalls@…>):
* resolution: => fixed
* status: assigned => closed
Comment:
In [changeset:"33a0a6f033b9243e0cc98e76bd494de73cf144eb" 33a0a6f0]:
{{{#!CommitTicketReference repository=""
revision="33a0a6f033b9243e0cc98e76bd494de73cf144eb"
Fixed #36791 -- Made MigrationAutodetector recreate through table when m2m
target model changes.
Co-Authored-By: Jacob Walls
<[email protected]>
Co-Authored-By: Clifford Gama <[email protected]>
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/36791#comment:15>
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 view this discussion visit
https://groups.google.com/d/msgid/django-updates/0107019b37fd394a-7e9d695c-e8a6-4a81-b1fb-135d959ebe45-000000%40eu-central-1.amazonses.com.
