summaryrefslogtreecommitdiff
path: root/docs/releases/2.0.txt
diff options
context:
space:
mode:
authorSimon Charette <charette.s@gmail.com>2017-11-26 22:39:43 -0500
committerSimon Charette <charette.s@gmail.com>2017-12-01 22:12:24 -0500
commit095c1aaa898bed40568009db836aa8434f1b983d (patch)
treefe6002bd40b12bedb73a683120c7f2407024590d /docs/releases/2.0.txt
parent474bd7a5d4b0b47eeedc03ad471ae9e630e95258 (diff)
Fixed #28849 -- Fixed referenced table and column rename on SQLite.
Thanks Ramiro for the input and Tim for the review.
Diffstat (limited to 'docs/releases/2.0.txt')
-rw-r--r--docs/releases/2.0.txt7
1 files changed, 7 insertions, 0 deletions
diff --git a/docs/releases/2.0.txt b/docs/releases/2.0.txt
index 904597a033..34068a7a05 100644
--- a/docs/releases/2.0.txt
+++ b/docs/releases/2.0.txt
@@ -534,6 +534,13 @@ rebuild tables using a script similar to this::
This script hasn't received extensive testing and needs adaption for various
cases such as multiple databases. Feel free to contribute improvements.
+In addition, because of a table alteration limitation of SQLite, it's prohibited
+to perform :class:`~django.db.migrations.operations.RenameModel` and
+:class:`~django.db.migrations.operations.RenameField` operations on models or
+fields referenced by other models in a transaction. In order to allow migrations
+containing these operations to be applied, you must set the
+``Migration.atomic`` attribute to ``False``.
+
Miscellaneous
-------------