p31829507
/
django
mirror of https://github.com/django/django.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Fixed #26962 -- Doc'd running migrations in transactions.

This commit is contained in:
Caio Ariede 2020-10-19 09:45:04 -03:00 committed by Mariusz Felisiak
parent 302caa40e4
commit 9ca22c7733
1 changed files with 21 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
docs/topics/migrations.txt
View File

@ -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
============