test0908
/
django
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Refs #31320 -- Warned against using BEGIN/COMMIT in RunSQL.

This commit is contained in:
Adam Johnson 2020-04-01 09:58:41 +01:00 committed by GitHub
parent 5c24c16e68
commit e9b014fbc5
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 10 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
docs/ref/migration-operations.txt
View File

@ -252,6 +252,12 @@ features of database backends that Django doesn't support directly.
the database. On most database backends (all but PostgreSQL), Django will the database. On most database backends (all but PostgreSQL), Django will
split the SQL into individual statements prior to executing them. split the SQL into individual statements prior to executing them.
.. warning::
On PostgreSQL and SQLite, only use ``BEGIN`` or ``COMMIT`` in your SQL in
:ref:`non-atomic migrations <non-atomic-migrations>`, to avoid breaking
Django's transaction state.
You can also pass a list of strings or 2-tuples. The latter is used for passing You can also pass a list of strings or 2-tuples. The latter is used for passing
queries and parameters in the same way as :ref:`cursor.execute() queries and parameters in the same way as :ref:`cursor.execute()
<executing-custom-sql>`. These three operations are equivalent:: <executing-custom-sql>`. These three operations are equivalent::
@ -275,12 +281,12 @@ insertion with a deletion::
If ``reverse_sql`` is ``None`` (the default), the ``RunSQL`` operation is If ``reverse_sql`` is ``None`` (the default), the ``RunSQL`` operation is
irreversible. irreversible.
The ``state_operations`` argument is so you can supply operations that are The ``state_operations`` argument allows you to supply operations that are
equivalent to the SQL in terms of project state; for example, if you are equivalent to the SQL in terms of project state. For example, if you are
manually creating a column, you should pass in a list containing an ``AddField`` manually creating a column, you should pass in a list containing an ``AddField``
operation here so that the autodetector still has an up-to-date state of the operation here so that the autodetector still has an up-to-date state of the
model (otherwise, when you next run ``makemigrations``, it won't see any model. If you don't, when you next run ``makemigrations``, it won't see any
operation that adds that field and so will try to run it again). For example:: operation that adds that field and so will try to run it again. For example::
migrations.RunSQL( migrations.RunSQL(
"ALTER TABLE musician ADD COLUMN name varchar(255) NOT NULL;", "ALTER TABLE musician ADD COLUMN name varchar(255) NOT NULL;",