#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 --------------------------------------+------------------------------------ Changes (by Tim Graham <timograham@…>):
* status: assigned => closed * resolution: => fixed Comment: In [changeset:"ad191d9e011f37d79a7f2df3da881b06539aaaea" ad191d9]: {{{ #!CommitTicketReference repository="" revision="ad191d9e011f37d79a7f2df3da881b06539aaaea" Fixed #29895 -- Doc'd why MySQL's atomic DDL statements don't work for atomic migrations. }}} -- Ticket URL: <https://code.djangoproject.com/ticket/29895#comment:8> 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/065.015a77f2c17f19e3cbc597e773a88b9a%40djangoproject.com. For more options, visit https://groups.google.com/d/optout.