#36061: Custom data migration for M2M with through_fields not working
-------------------------------------+-------------------------------------
Reporter: Brian Nettleton | Owner: Brian
| Nettleton
Type: Bug | Status: closed
Component: Migrations | Version: 4.2
Severity: Normal | Resolution: fixed
Keywords: through_fields | Triage Stage: Ready for
migration | checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Sarah Boyce <42296566+sarahboyce@…>):
In [changeset:"b96e4c04b666b1044555d7a32f64e83cbad57b03" b96e4c04]:
{{{#!CommitTicketReference repository=""
revision="b96e4c04b666b1044555d7a32f64e83cbad57b03"
[5.2.x] Fixed #36061 -- Added migration support for
ManyToManyField.through_fields.
Added through_fields support to ManyToManyField.deconstruct.
Thanks to Simon Charette for pointers and the review.
Backport of b13b8684a04d0bc1081104c5973c62c27dc673b0 from main.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/36061#comment:7>
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/01070194dba91169-9f3485f0-d115-4d17-b1e9-7a8021796017-000000%40eu-central-1.amazonses.com.
