#36611: Model validation of constraint involving ForeignObject considers only
first
column
-------------------------------------+-------------------------------------
Reporter: Jacob Walls | Owner: (none)
Type: Bug | Status: new
Component: Database layer | Version: 5.2
(models, ORM) |
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Sarah Boyce):
In #35992, we added a system check to say that `CompositePrimaryKey`
fields cannot be used in indexes/constraints/unique_together
We could perhaps have approached #36580 with a similar system check, and
maybe that option is still open (so we disallow ForeignObject fields in
indexes/constraints/unique_together)
--
Ticket URL: <https://code.djangoproject.com/ticket/36611#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/0107019960f184dc-d2eafead-5d4c-46a4-8134-d78e41716bf1-000000%40eu-central-1.amazonses.com.
