Refs #25144 -- Revised deprecation timeline: migrations won't become compulsory.
This commit is contained in:
parent
721d8e50ac
commit
e133b55943
|
@ -289,9 +289,12 @@ details on these changes.
|
|||
* ``allow_syncdb`` on database routers will no longer automatically become
|
||||
``allow_migrate``.
|
||||
|
||||
* The legacy method of syncing apps without migrations will be removed,
|
||||
and migrations will become compulsory for all apps. This includes automatic
|
||||
loading of ``initial_data`` fixtures and support for initial SQL data.
|
||||
* Automatic syncing of apps without migrations will be removed. Migrations will
|
||||
become compulsory for all apps unless you pass the ``--run-syncdb`` option to
|
||||
``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
|
||||
declare an explicit :attr:`~django.db.models.Options.app_label`.
|
||||
|
|
Loading…
Reference in New Issue