summaryrefslogtreecommitdiff
path: root/docs/topics
diff options
context:
space:
mode:
authorTim Graham <timograham@gmail.com>2019-01-26 16:34:50 -0500
committerTim Graham <timograham@gmail.com>2019-01-28 10:30:36 -0500
commite8cb0dcc19c4bcabee1d856b7fae1b54fa3e3380 (patch)
tree1926b037919a8cfbdeed4d8614810d3a0eb3974e /docs/topics
parent56f7f5026d5a6c9df7c4366f529ca136a0b03ff4 (diff)
[2.2.x] Refs #30033 -- Doc'd change regarding apps without migrations depending on apps with migrations.
The addition of self.connection.check_constraints() in 7289874adceec46b5367ec3157cdd10c711253a0 is the cause. Backport of fcfb7306586184f08c7f75c174f95b54a212320d from master.
Diffstat (limited to 'docs/topics')
-rw-r--r--docs/topics/migrations.txt4
1 files changed, 4 insertions, 0 deletions
diff --git a/docs/topics/migrations.txt b/docs/topics/migrations.txt
index 2f33b97878..4df05bdd67 100644
--- a/docs/topics/migrations.txt
+++ b/docs/topics/migrations.txt
@@ -191,6 +191,10 @@ restrict to a single app. Restricting to a single app (either in
a guarantee; any other apps that need to be used to get dependencies correct
will be.
+Apps without migrations must not have relations (``ForeignKey``,
+``ManyToManyField``, etc.) to apps with migrations. Sometimes it may work, but
+it's not supported.
+
.. _migration-files:
Migration files