[1.7.x] Bump DatabaseCreation deprecation to 2.0 (refs #22340)
Backport of 61da5f3f02
from master
This commit is contained in:
parent
1ed876ee5b
commit
10327be1f3
|
@ -7,11 +7,6 @@ in a backward incompatible way, following their deprecation, as per the
|
|||
:ref:`deprecation policy <internal-release-deprecation-policy>`. More details
|
||||
about each item can often be found in the release notes of two versions prior.
|
||||
|
||||
.. _deprecation-removed-in-2.0:
|
||||
|
||||
2.0
|
||||
---
|
||||
|
||||
.. _deprecation-removed-in-1.9:
|
||||
|
||||
1.9
|
||||
|
@ -36,13 +31,6 @@ details on these changes.
|
|||
* ``allow_syncdb`` on database routers will no longer automatically become
|
||||
``allow_migrate``.
|
||||
|
||||
* The ``DatabaseCreation`` class on each database backend will be removed,
|
||||
and all table/schema editing will be moved to be via ``SchemaEditor`` instead.
|
||||
|
||||
* The legacy method of syncing apps without migrations will be removed,
|
||||
and migrations will become compulsory for all apps. This includes automatic
|
||||
loading of fixtures and support for initial SQL data.
|
||||
|
||||
* All models will need to be defined inside an installed application or
|
||||
declare an explicit :attr:`~django.db.models.Options.app_label`.
|
||||
Furthermore, it won't be possible to import them before their application
|
||||
|
|
Loading…
Reference in New Issue