#32635: Creating a UniqueConstraint with condition referencing OneToOneField
generates invalid SQL
-------------------------------------+-------------------------------------
Reporter: sim1234 | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 2.2
(models, ORM) |
Severity: Normal | Resolution:
Keywords: UniqueConstraint | Triage Stage: Accepted
OneToOneField |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Simon Charette):
* type: Uncategorized => Bug
* component: Uncategorized => Database layer (models, ORM)
* stage: Unreviewed => Accepted
Comment:
I could swear this was discussed already but both `conditions` and
`expressions` for `Index` and `Constrant` should be checked. This should
be achievable through the use `allow_joins=False` at resolving time.
--
Ticket URL: <https://code.djangoproject.com/ticket/32635#comment:1>
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 on the web visit
https://groups.google.com/d/msgid/django-updates/065.ff443bc354c3458e9ad66d7684f71812%40djangoproject.com.
