#31440: Add a standard way to set deferrable constraints
-------------------------------------+-------------------------------------
Reporter: Ian Foote | Owner: nobody
Type: New feature | Status: new
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
Keywords: constraints | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Description changed by Ian Foote:
Old description:
> The behaviour of deferrable constraints (e.g. Foreign Key, Unique) in a
> transaction can be modified using the `SET CONSTRAINTS` sql syntax
> (https://www.postgresql.org/docs/12/sql-set-constraints.html). Supporting
> this directly in Django will allow extra control over when
> `IntegrityError` is raised.
New description:
The behaviour of deferrable constraints (e.g. Foreign Key, Unique) in a
transaction can be modified using the `SET CONSTRAINTS` sql syntax
(https://www.postgresql.org/docs/12/sql-set-constraints.html). Supporting
this directly in Django will allow extra control over when
`IntegrityError` is raised.
Related to #20581.
--
--
Ticket URL: <https://code.djangoproject.com/ticket/31440#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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.5546dc13c37601ebc3d4abedd6fa409f%40djangoproject.com.
