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

Refs #30033 -- Doc'd change regarding apps without migrations depending on apps with migrations. 

The addition of self.connection.check_constraints() in
7289874adc is the cause.
This commit is contained in:
Tim Graham 2019-01-26 16:34:50 -05:00
parent 7e3bf2662b
commit fcfb730658
2 changed files with 11 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
docs/releases/2.2.txt
View File

@ -446,6 +446,13 @@ Miscellaneous
:class:`~django.db.models.Variance` aggregate functions now return a :class:`~django.db.models.Variance` aggregate functions now return a
``Decimal`` instead of a ``float`` when the input is ``Decimal``. ``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: .. _deprecated-features-2.2:
Features deprecated in 2.2 Features deprecated in 2.2

4
docs/topics/migrations.txt
View File

@ -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 a guarantee; any other apps that need to be used to get dependencies correct
will be. 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:
Migration files Migration files