#29895: Adjust atomic DDL documentation to avoid ambiguity with MySQL 8+ notion 
of
atomic DDL.
--------------------------------------+------------------------------------
     Reporter:  Nathan Klug           |                    Owner:  Rodrigo
         Type:  Cleanup/optimization  |                   Status:  assigned
    Component:  Documentation         |                  Version:  2.1
     Severity:  Normal                |               Resolution:
     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 Rodrigo):

 * has_patch:  0 => 1


Old description:

> I noticed that Django's documentation says "The atomic attribute doesn’t
> have an effect on databases that don’t support DDL transactions (e.g.
> MySQL, Oracle)." here: https://docs.djangoproject.com/en/2.1/howto
> /writing-migrations/#non-atomic-migrations
>
> I noticed that MySQL 8 adds support for atomic DDL statements though
> (https://dev.mysql.com/doc/refman/8.0/en/atomic-ddl.html). Is this
> something that Django supports when using MySQL 8 and the documentation
> is imprecise (if so, consider this a bug report to clarify
> documentation)? or is this not yet supported (if so, consider this a
> feature request)? Thanks!

New description:

 I noticed that Django's documentation says "The atomic attribute doesn’t
 have an effect on databases that don’t support DDL transactions (e.g.
 MySQL, Oracle)." here: https://docs.djangoproject.com/en/2.1/howto
 /writing-migrations/#non-atomic-migrations

 I noticed that MySQL 8 adds support for atomic DDL statements though
 (https://dev.mysql.com/doc/refman/8.0/en/atomic-ddl.html). Is this
 something that Django supports when using MySQL 8 and the documentation is
 imprecise (if so, consider this a bug report to clarify documentation)? or
 is this not yet supported (if so, consider this a feature request)?
 Thanks!

 https://github.com/math-a3k/django/pull/1

--

-- 
Ticket URL: <https://code.djangoproject.com/ticket/29895#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 [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.5ee81dc2914b6e23b197e8cd5e904b1a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to