From 9ca22c7733efeeb140b75585c6387ef2cb861d19 Mon Sep 17 00:00:00 2001
From: Caio Ariede <caio.ariede@gmail.com>
Date: Mon, 19 Oct 2020 09:45:04 -0300
Subject: [PATCH] Fixed #26962 -- Doc'd running migrations in transactions.

---
 docs/topics/migrations.txt | 21 +++++++++++++++++++++
 1 file changed, 21 insertions(+)

diff --git a/docs/topics/migrations.txt b/docs/topics/migrations.txt
index b0d75a4f09c..708040826f6 100644
--- a/docs/topics/migrations.txt
+++ b/docs/topics/migrations.txt
@@ -169,6 +169,27 @@ migrations for you. If not, you'll have to go in and modify the migrations
 yourself - don't worry, this isn't difficult, and is explained more in
 :ref:`migration-files` below.
 
+Transactions
+============
+
+On databases that support DDL transactions (SQLite and PostgreSQL), all
+migration operations will run inside a single transaction by default. In
+contrast, if a database doesn't support DDL transactions (e.g. MySQL, Oracle)
+then all operations will run without a transaction.
+
+You can prevent a migration from running in a transaction by setting the
+``atomic`` attribute to ``False``. For example::
+
+    from django.db import migrations
+
+    class Migration(migrations.Migration):
+        atomic = False
+
+It's also possible to execute parts of the migration inside a transaction using
+:func:`~django.db.transaction.atomic()` or by passing ``atomic=True`` to
+:class:`~django.db.migrations.operations.RunPython`. See
+:ref:`non-atomic-migrations` for more details.
+
 Dependencies
 ============