Updated release notes on app_label.
Django determines automatically which application models belong to, provided the application can be imported without importing models.
This commit is contained in:
parent
30a42a4fc3
commit
1386075f62
|
@ -33,7 +33,7 @@ Available ``Meta`` options
|
||||||
.. versionadded:: 1.7
|
.. versionadded:: 1.7
|
||||||
|
|
||||||
``app_label`` is no longer required for models that are defined
|
``app_label`` is no longer required for models that are defined
|
||||||
in a ``models`` package within an app.
|
outside the ``models`` module of an application.
|
||||||
|
|
||||||
``db_table``
|
``db_table``
|
||||||
------------
|
------------
|
||||||
|
|
|
@ -466,9 +466,6 @@ Models
|
||||||
``Meta`` option allows you to customize (or disable) creation of the default
|
``Meta`` option allows you to customize (or disable) creation of the default
|
||||||
add, change, and delete permissions.
|
add, change, and delete permissions.
|
||||||
|
|
||||||
* :attr:`~django.db.models.Options.app_label` is no longer required for models
|
|
||||||
that are defined in a ``models`` package within an app.
|
|
||||||
|
|
||||||
* Explicit :class:`~django.db.models.OneToOneField` for
|
* Explicit :class:`~django.db.models.OneToOneField` for
|
||||||
:ref:`multi-table-inheritance` are now discovered in abstract classes.
|
:ref:`multi-table-inheritance` are now discovered in abstract classes.
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue