#36198: Unique Constraints defined with __date lookups on F expressions fail
validation but create database constraints sucessfully
-------------------------------------+-------------------------------------
Reporter: Tom Hall | Owner: (none)
Type: Bug | Status: new
Component: Database layer | Version: 5.1
(models, ORM) |
Severity: Normal | Resolution:
Keywords: constraint lookup | Triage Stage: Accepted
unique validation |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Simon Charette):
Submitted [https://github.com/django/django/pull/19190 a PR] demonstrating
how this can be implemented for `F.resolve_expression` without going fully
unboard with the `Unresolved(Lookup|Transform)` approach that might be
necessary to fully resolve #34871.
--
Ticket URL: <https://code.djangoproject.com/ticket/36198#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/010701951a2e7ec8-4e17102d-4790-4eca-9dff-940ecd3bc16f-000000%40eu-central-1.amazonses.com.
