#30490: migrations unique_index on (app, name).
-------------------------------------+-------------------------------------
Reporter: Richard | Owner: nobody
Kojedzinszky |
Type: Bug | Status: closed
Component: Uncategorized | Version: master
Severity: Normal | Resolution: wontfix
Keywords: migrations parallel | Triage Stage:
run | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Richard Kojedzinszky):
That is why I wrote, that my approach might not be the best practice. With
an automated deployments, I would really like the case when Django itself
would prevent applying the migrations multiple times. That would even help
preventing errors made by humans. You are right, the whole migration step
should be in one database transaction for this to work. And as it is now,
I rather think it is a bug.
--
Ticket URL: <https://code.djangoproject.com/ticket/30490#comment:2>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/071.e9d6ac171e295ee13e8f1f9860813f66%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
