summaryrefslogtreecommitdiff
path: root/docs/releases/2.2.txt
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:05:25 -0500
commitfcfb7306586184f08c7f75c174f95b54a212320d (patch)
tree6645cf43ce69099ce2b6483aad5899b4e37f4b59 /docs/releases/2.2.txt
parent7e3bf2662b5dedeb47856adc18a9378e2d10a599 (diff)
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.
Diffstat (limited to 'docs/releases/2.2.txt')
-rw-r--r--docs/releases/2.2.txt7
1 files changed, 7 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