#29895: Adjust atomic DDL documentation to avoid ambiguity with MySQL 8+ notion
of
atomic DDL.
--------------------------------------+------------------------------------
Reporter: Nathan Klug | Owner: Rodrigo
Type: Cleanup/optimization | Status: closed
Component: Documentation | Version: 2.1
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Comment (by Tim Graham <timograham@…>):
In [changeset:"4c506730b5a8dae2ab9a16712db2f39c21d4385a" 4c50673]:
{{{
#!CommitTicketReference repository=""
revision="4c506730b5a8dae2ab9a16712db2f39c21d4385a"
[2.1.x] Fixed #29895 -- Doc'd why MySQL's atomic DDL statements don't work
for atomic migrations.
Backport of ad191d9e011f37d79a7f2df3da881b06539aaaea from master.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/29895#comment:9>
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/065.d07a567d04ca642bed0a4e0a8c2a4348%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
