diff options
| author | Rodrigo <matematica.a3k@gmail.com> | 2018-12-03 21:37:28 -0500 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2018-12-06 16:45:39 -0500 |
| commit | 4c506730b5a8dae2ab9a16712db2f39c21d4385a (patch) | |
| tree | bade2158008287773c498d4c26b199e25d0d40c5 | |
| parent | 389ef05b1b74dcebcaf5b6885a9ff00ceccdb737 (diff) | |
[2.1.x] Fixed #29895 -- Doc'd why MySQL's atomic DDL statements don't work for atomic migrations.
Backport of ad191d9e011f37d79a7f2df3da881b06539aaaea from master.
| -rw-r--r-- | docs/howto/writing-migrations.txt | 5 |
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 =================================== |