#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
-------------------------------------+-------------------------------------
Changes (by felixxm):
* status: new => closed
* version: 1.11 => master
* resolution: => wontfix
Comment:
Thanks for the report, however it is rather a support issue, IMO. Adding
unique on `(app, name)` will not fix your issue, because Django adds entry
to the table with migrations history outside the main transaction.
First of all I would use `select_for_update()` to lock table before update
(to prevent race condition). Secondly you should run migrations (on the
same database) only on one instance.
Closing per TicketClosingReasons/UseSupportChannels.
--
Ticket URL: <https://code.djangoproject.com/ticket/30490#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 [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.43c0e7dee924857df850435f889aa102%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
