From 2ea1e70b85fee2ee1229c62b82ae283bea68cb73 Mon Sep 17 00:00:00 2001 From: Moayad Mardini Date: Tue, 27 May 2014 21:53:19 +0300 Subject: [PATCH] Fixed #22601 -- Added a note about model inheritance. Thanks semenov for the report. --- docs/topics/db/models.txt | 13 ++++++++----- 1 file 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.