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

Refs #25144 -- Revised deprecation timeline: migrations won't become compulsory.

This commit is contained in:
Tim Graham 2015-08-31 10:40:45 -04:00
parent 721d8e50ac
commit e133b55943
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

@ -289,9 +289,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`.