Changes between Initial Version and Version 1 of Ticket #29824
- Timestamp:
- Oct 4, 2018, 6:02:19 AM (6 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #29824 – Description
initial v1 1 1 A lot of work was done to add the check constraint to Django 2.2. On top of such a constraint, PostgreSQL has an exclusion constraint that works well on ranges, regardless if they're represented using two fields, or a single field using a range-type. Essentially, this constraint enforces a unique constraint for ranges, with a possibility for an additional check. 2 2 3 https://github.com/tbicr/django-pg-zero-downtime-migrations/ uses `ALTER TABLE %(table)s VALIDATE CONSTRAINT` to restrict how long the table is locked for writing. I was contemplating to touch this subject in the patch. 3 https://github.com/tbicr/django-pg-zero-downtime-migrations/ uses `ALTER TABLE %(table)s VALIDATE CONSTRAINT` to restrict how long the table is locked for writing. I was contemplating to touch this subject in the patch. 4 5 [https://github.com/django/django/pull/10478 PR]