#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 Simon Charette):
Sarah, I know it represents reverting back work but I do like this
approach. We could revisit once we we add support for generic composite
fields but until then baking hacks to support what is essentially ORM
sugar (that can be expressed by pointing at the concrete fields directly)
makes me feel like we're opening the door to unbounded work.
--
Ticket URL: <https://code.djangoproject.com/ticket/36611#comment:8>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/0107019961ddc743-45bb971a-8117-4787-8615-624507a2b01f-000000%40eu-central-1.amazonses.com.
