Django/django
11
0
Fork 0
Code Pull Requests Projects Releases Activity

[1.8.x] Refs #25144 -- Revised deprecation timeline: migrations won't become compulsory.

Browse Source 
Backport of e133b55943f26e87cff5b22215a776a9ce3fc6f3 from master
This commit is contained in:
Tim Graham 2015-08-31 10:40:45 -04:00
parent 7dabaa8ee3
commit 20dfd02db0
1 changed files with 6 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
docs/internals/deprecation.txt
View File

@ -196,9 +196,12 @@ details on these changes.
* ``allow_syncdb`` on database routers will no longer automatically become * ``allow_syncdb`` on database routers will no longer automatically become
``allow_migrate``. ``allow_migrate``.
* The legacy method of syncing apps without migrations will be removed, * Automatic syncing of apps without migrations will be removed. Migrations will
and migrations will become compulsory for all apps. This includes automatic become compulsory for all apps unless you pass the ``--run-syncdb`` option to
loading of ``initial_data`` fixtures and support for initial SQL data. ``migrate``.
* Support for automatic loading of ``initial_data`` fixtures and initial SQL
data will be removed.
* All models will need to be defined inside an installed application or * All models will need to be defined inside an installed application or
declare an explicit :attr:`~django.db.models.Options.app_label`. declare an explicit :attr:`~django.db.models.Options.app_label`.