Opened 4 years ago
Last modified 4 years ago
#31440 closed New feature
Add a standard way to set deferrable constraints — at Initial Version
| Reported by: | Ian Foote | Owned by: | nobody |
|---|---|---|---|
| Component: | Database layer (models, ORM) | Version: | dev |
| Severity: | Normal | Keywords: | constraints |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
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.
Note:
See TracTickets
for help on using tickets.