#36627: Support PostgreSQL 18+ temporal constraints
----------------------------------+--------------------------------------
Reporter: Adam Johnson | Owner: (none)
Type: New feature | Status: new
Component: contrib.postgres | Version: dev
Severity: Normal | Resolution:
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 Simon Charette):
* type: Uncategorized => New feature
Comment:
If we are to accept this ticket I suggest we focus it on the
`UniqueConstraint` case and then consider `CompositePrimaryKey` and
foreign support once #35956 lands.
The hard part here will likely not be to write the `WithoutOverlaps`
expression part but to adjust `UniqueConstraint.validate` to honor it
without coupling `contrib.postgres` and core.
I'll note that `WITHOUT OVERLAPS` is really just SQL sugar over exclusion
constraints which we already support via `ExclusionConstraint` so I'm not
entirely convinced it's worth adding given the `UniqueConstraint.validate`
complexity it would incur.
--
Ticket URL: <https://code.djangoproject.com/ticket/36627#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 visit
https://groups.google.com/d/msgid/django-updates/0107019988e2c008-0ac77d0a-ba14-4701-9a06-9765eb5f277a-000000%40eu-central-1.amazonses.com.
