summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
Diffstat (limited to 'docs')
-rw-r--r--docs/releases/2.2.txt7
-rw-r--r--docs/topics/migrations.txt4
2 files changed, 11 insertions, 0 deletions
diff --git a/docs/releases/2.2.txt b/docs/releases/2.2.txt
index b988fd185c..941e0f5421 100644
--- a/docs/releases/2.2.txt
+++ b/docs/releases/2.2.txt
@@ -446,6 +446,13 @@ Miscellaneous
:class:`~django.db.models.Variance` aggregate functions now return a
``Decimal`` instead of a ``float`` when the input is ``Decimal``.
+* Tests will fail on SQLite if apps without migrations have relations to apps
+ with migrations. This has been a documented restriction since migrations were
+ added in Django 1.7, but it fails more reliably now. You'll see tests failing
+ with errors like ``no such table: <app_label>_<model>``. This was observed
+ with several third-party apps that had tests models without migrations. You
+ must add migrations for such models.
+
.. _deprecated-features-2.2:
Features deprecated in 2.2
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