#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 Adam (Chainz) Johnson):
You don't need to use Redis for distributed locking, you can use advisory
locking in your database server. They can live outside of transactions.
In PostgreSQL they are called advisory locks -
https://hashrocket.com/blog/posts/advisory-locks-in-postgres . They are by
an integer key.
In MySQL/MariaDB they are called user locks -
https://mariadb.com/kb/en/library/get_lock/ . They are by a string key.
I don't know about SQLite or Oracle. Quick internet searches don't reveal
anything
Potentially Django could use these advisory locks.
--
Ticket URL: <https://code.djangoproject.com/ticket/30490#comment:6>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/071.94432595c96d26a6cc57641a68d1a72f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
