#36530: System check for ManyToManyField & Composite Primary Key checks only one
direction
-------------------------------------+-------------------------------------
Reporter: Jacob Walls | Owner: Jason
| Hall
Type: Bug | Status: closed
Component: Database layer | Version: 5.2
(models, ORM) |
Severity: Release blocker | Resolution: fixed
Keywords: compositeprimarykey | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Natalia <124304+nessita@…>):
In [changeset:"bdc3f9e3508fc144c5e9710f5b672cc41f6e742d" bdc3f9e]:
{{{#!CommitTicketReference repository=""
revision="bdc3f9e3508fc144c5e9710f5b672cc41f6e742d"
[5.2.x] Fixed #36530 -- Extended fields.E347 to check for ManyToManyField
involving CompositePrimaryKey on either side.
Thanks to Jacob Walls for the report.
Backport of 2013092b693be0ebdf36f41dc61615a2de1bbe31 from main.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/36530#comment:14>
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/010701987a0ff5bd-e6573fec-e119-495f-a660-165f7933868a-000000%40eu-central-1.amazonses.com.
