#30773: Support Algorithm parameter on MySQL migrations.
-----------------------------+--------------------------------------
Reporter: mklauber | Owner: nobody
Type: New feature | Status: new
Component: Migrations | Version: master
Severity: Normal | Resolution:
Keywords: mysql | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------+--------------------------------------
Comment (by Simon Charette):
MySQL will use the best algorithm available by default if possible
(`INPLACE` or `INSTANT`) so this option will only make the operation crash
if the specified algorithm is not available. Given MySQL doesn't support
transactional DDL this has the potential to cause more harm than good IMO.
I guess we could add support for `algorithm` to MySQL schema editor but as
I mentioned above MySQL already picks the ''best'' algorithm it can and I
can't see a reason for using `COPY` or `INPLACE` when `INSTANT` is
supported.
Finally given we added `AddIndexConcurrently` to `contrib.postgres` this
would probably belong in `django-mysql`.
--
Ticket URL: <https://code.djangoproject.com/ticket/30773#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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.a2ee370d48b2593c2f10ab856df1cc22%40djangoproject.com.
