From fbae9c0e023aea2666feb1603ece172548342ec1 Mon Sep 17 00:00:00 2001 From: ovalseven8 Date: Tue, 6 Mar 2018 17:18:49 +0100 Subject: [1.11.x] Fixed #29192 -- Removed inaccurate statement regarding overriding fields from abstract base classes. Partial backport of 22bcd3a1d88add6e4cf2c4451ede8d1ae142dedd from master --- docs/topics/db/models.txt | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) (limited to 'docs') diff --git a/docs/topics/db/models.txt b/docs/topics/db/models.txt index f4034f6ba7..944b944e0e 100644 --- a/docs/topics/db/models.txt +++ b/docs/topics/db/models.txt @@ -899,9 +899,7 @@ information into a number of other models. You write your base class and put ``abstract=True`` in the :ref:`Meta ` class. This model will then not be used to create any database table. Instead, when it is used as a base class for other models, its -fields will be added to those of the child class. It is an error to -have fields in the abstract base class with the same name as those in -the child (and Django will raise an exception). +fields will be added to those of the child class. An example:: -- cgit v1.3