#22073: Backwards migration on ManyToMany field does not remove intermediary
table
---------------------------------+----------------------------------------
Reporter: bendavis78 | Owner: andrewgodwin
Type: Bug | Status: closed
Component: Migrations | Version: master
Severity: Release blocker | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+----------------------------------------
Comment (by Andrew Godwin <andrew@…>):
In [changeset:"cdf6eba1816669bd77a28da903d931b5a4b15992"]:
{{{
#!CommitTicketReference repository=""
revision="cdf6eba1816669bd77a28da903d931b5a4b15992"
Merge pull request #2315 from bendavis78/issues/22073
Fixed #22073 - Ensure CreateTable operation handles backwards migration
correctly when M2M fields are present
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/22073#comment:8>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.54625cf4bf3b24848ab6cab129a3fb07%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
