#33652: migrations: skip insertion of exclusion constraints when not using
postgres
-------------------------------------+-------------------------------------
Reporter: hottwaj | Owner: nobody
Type: New | Status: new
feature |
Component: Database | Version: dev
layer (models, ORM) | Keywords: postgres exclusion
Severity: Normal | constraint
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
Exclusion constraints are only supported by postgres, and using them with
e.g. a sqlite backend causes an exception during migrations when django
attempts to insert them into the DB.
Could exclusion constraints be skipped when migrations are run for non-
postgres backends instead? Perhaps with a warning that they are being
skipped?
This would help in situations where multiple backends are used for
testing/prototyping purposes
--
Ticket URL: <https://code.djangoproject.com/ticket/33652>
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 on the web visit
https://groups.google.com/d/msgid/django-updates/0107018042216b9d-51867278-6763-4381-bc71-c998c2bce017-000000%40eu-central-1.amazonses.com.
