#29895: Adjust atomic DDL documentation to avoid ambiguity with MySQL 8+ notion
of
atomic DDL.
--------------------------------------+------------------------------------
Reporter: Nathan Klug | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Documentation | Version: 2.1
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Changes (by Simon Charette):
* component: Migrations => Documentation
* type: New feature => Cleanup/optimization
Comment:
Thanks for the investigation Tom.
> When using atomic DDL in mysql certain statements immediately and
implicitly commit the transaction...
Yeah that's the exact opposite of what Django means by ''atomic DDL'' as
what PostgreSQL and SQLite support.
I've repurposed the ticket to be a documentation adjustment instead.
--
Ticket URL: <https://code.djangoproject.com/ticket/29895#comment:4>
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.5b7e7b34e9f7df37640469393bcaa266%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
