#36530: System check for ManyToManyField & Composite Primary Key checks only one
direction
-------------------------------------+-------------------------------------
Reporter: Jacob Walls | Owner: Jason
| Hall
Type: Bug | Status: assigned
Component: Database layer | Version: 5.2
(models, ORM) |
Severity: Release blocker | Resolution:
Keywords: compositeprimarykey | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Jacob Walls):
We should use `CompositePrimaryKey`, as that ensures the check guards what
is unsupported in fact.
Natalia's version riffs on the tests from #36034, which is what I had in
mind. And incidentally why I thought this was an easy picking, but I
suppose I should go to the forum before taking up a 1-person campaign to
use that flag more ;)
--
Ticket URL: <https://code.djangoproject.com/ticket/36530#comment:4>
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/0107019851ae590a-4df673a5-311e-4cc7-a1f4-626eb6c69246-000000%40eu-central-1.amazonses.com.
