#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
----------------------------------+--------------------------------------
Comment (by Adam Johnson):
Yes, it seems to be PostgreSQL-only. But the SQL syntax *is* much easier
to use, and it would be similarly so within Django models, which should
help with adoption of exclusion/temporal constraints.
--
Ticket URL: <https://code.djangoproject.com/ticket/36627#comment:2>
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/010701998cf2deba-52edcc57-7b9a-47e6-bb28-2a5fa028bbbc-000000%40eu-central-1.amazonses.com.
