#34610: Django_migrations unique constraint
-------------------------------------+-------------------------------------
Reporter: Richard | Owner: nobody
Kojedzinszky |
Type: New | Status: new
feature |
Component: Database | Version: 4.2
layer (models, ORM) |
Severity: Normal | Keywords:
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
I suggest to add an unique constraint on django_migrations(app, name) to
even improve migration atomicity, db consistency. With that most paralelly
run migrations should fail. With db engines supporting (e.g. postgres) it
will prevent migrations repeated. With db engines not supporting this it
will at least report errors during migration runs.
--
Ticket URL: <https://code.djangoproject.com/ticket/34610>
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/01070188708c4a03-3111cd5b-5ab5-409c-bbf5-1f344fc5bb03-000000%40eu-central-1.amazonses.com.
