summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorRodrigo <matematica.a3k@gmail.com>2018-12-03 21:37:28 -0500
committerTim Graham <timograham@gmail.com>2018-12-06 16:03:02 -0500
commitad191d9e011f37d79a7f2df3da881b06539aaaea (patch)
treeb882a56e665dac0f07be16c1ee4b507c5b6fbc57 /docs
parentf9a33e3c3f4cfbff60522cd54455e78c96a9d2a4 (diff)
Fixed #29895 -- Doc'd why MySQL's atomic DDL statements don't work for atomic migrations.
Diffstat (limited to 'docs')
-rw-r--r--docs/howto/writing-migrations.txt5
1 files changed, 4 insertions, 1 deletions
diff --git a/docs/howto/writing-migrations.txt b/docs/howto/writing-migrations.txt
index f98a56c534..084513b312 100644
--- a/docs/howto/writing-migrations.txt
+++ b/docs/howto/writing-migrations.txt
@@ -221,7 +221,10 @@ smaller batches::
]
The ``atomic`` attribute doesn't have an effect on databases that don't support
-DDL transactions (e.g. MySQL, Oracle).
+DDL transactions (e.g. MySQL, Oracle). (MySQL's `atomic DDL statement support
+<https://dev.mysql.com/doc/refman/en/atomic-ddl.html>`_ refers to individual
+statements rather than multiple statements wrapped in a transaction that can be
+rolled back.)
Controlling the order of migrations
===================================