diff options
| author | Moayad Mardini <moayad.m@gmail.com> | 2014-05-27 21:53:19 +0300 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2014-05-27 19:42:16 -0400 |
| commit | 2ea1e70b85fee2ee1229c62b82ae283bea68cb73 (patch) | |
| tree | 921d2410908087bd0e2ee251c97cd207028b8a6a /docs | |
| parent | d0f7c7f59abaab88335c840f5a2d886434381100 (diff) | |
Fixed #22601 -- Added a note about model inheritance.
Thanks semenov for the report.
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/topics/db/models.txt | 13 |
1 files changed, 8 insertions, 5 deletions
diff --git a/docs/topics/db/models.txt b/docs/topics/db/models.txt index d883abf8ab..a1be192796 100644 --- a/docs/topics/db/models.txt +++ b/docs/topics/db/models.txt @@ -839,11 +839,14 @@ Model inheritance ================= Model inheritance in Django works almost identically to the way normal -class inheritance works in Python. The only decision you have to make -is whether you want the parent models to be models in their own right -(with their own database tables), or if the parents are just holders -of common information that will only be visible through the child -models. +class inheritance works in Python, but the basics at the beginning of the page +should still be followed. That means the base class should subclass +:class:`django.db.models.Model`. + +The only decision you have to make is whether you want the parent models to be +models in their own right (with their own database tables), or if the parents +are just holders of common information that will only be visible through the +child models. There are three styles of inheritance that are possible in Django. |
