#36611: Model validation of constraint involving ForeignObject considers only
first
column
-------------------------------------+-------------------------------------
Reporter: Jacob Walls | Owner: Jacob
| Walls
Type: Bug | Status: closed
Component: Database layer | Version: 5.2
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by nessita <124304+nessita@…>):
* resolution: => fixed
* status: assigned => closed
Comment:
In [changeset:"5b51e6f759f2ba993219347435149173c756c478" 5b51e6f]:
{{{#!CommitTicketReference repository=""
revision="5b51e6f759f2ba993219347435149173c756c478"
Fixed #36611, Refs #36580 -- Added system check for multicolumn
ForeignObject in Meta.indexes/constraints/unique_together.
ForeignObjects with multiple `from_fields` are not supported in these
options.
Co-authored-by: Jacob Walls <[email protected]>
Co-authored-by: Natalia <[email protected]>
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/36611#comment:17>
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/01070199deb4eed0-707a5e53-64b5-4e51-ad5a-8feb167b103a-000000%40eu-central-1.amazonses.com.
