summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorovalseven8 <ovalseven8@users.noreply.github.com>2018-03-06 17:18:49 +0100
committerTim Graham <timograham@gmail.com>2018-03-13 13:56:50 -0400
commitfbae9c0e023aea2666feb1603ece172548342ec1 (patch)
treefc0921ff0f1a51e24164af3405a046f00a4626d0 /docs
parentc8e5c1f4205078d8b58420cc585917384e51dab2 (diff)
[1.11.x] Fixed #29192 -- Removed inaccurate statement regarding overriding fields from abstract base classes.
Partial backport of 22bcd3a1d88add6e4cf2c4451ede8d1ae142dedd from master
Diffstat (limited to 'docs')
-rw-r--r--docs/topics/db/models.txt4
1 files changed, 1 insertions, 3 deletions
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 <meta-options>`
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::