#36627: Support PostgreSQL 18+ temporal constraints
----------------------------------+--------------------------------------
Reporter: Adam Johnson | Owner: (none)
Type: New feature | Status: closed
Component: contrib.postgres | Version: dev
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------------+--------------------------------------
Changes (by Jacob Walls):
* resolution: => wontfix
* status: new => closed
Comment:
Thanks all, please continue this discussion at django/new-features. Any
level of effort estimate you would have on `UniqueConstraint.validate` and
Simon's concern about contrib.postgres-specific flavors of
`UniqueConstraint` would be helpful.
--
Ticket URL: <https://code.djangoproject.com/ticket/36627#comment:3>
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/01070199958f7b50-49d74471-89fd-4ecb-9ec2-b0cd4c0adfb6-000000%40eu-central-1.amazonses.com.
