mirrors/django
mirrors/django
0
0
Fork 0
mirror of https://github.com/django/django.git synced 2024-12-01 15:42:04 +01:00
Code Issues Releases Wiki Activity

Fixed #14629 -- corrected a misspelling and poor wording in the docs. Thanks to OldTroll for the patch.

Browse Source 
git-svn-id: http://code.djangoproject.com/svn/django/trunk@14466 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Alex Gaynor 2010-11-06 03:26:17 +00:00
parent 56ae68c92f
commit cf03598eec
1 changed files with 2 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
docs/topics/db/models.txt
View File

@ -1213,11 +1213,11 @@ cannot create another model field called ``author`` in any class that inherits
from that base class.
Overriding fields in a parent model leads to difficulties in areas such as
initialising new instances (specifying which field is being intialised in
initialising new instances (specifying which field is being initialized in
``Model.__init__``) and serialization. These are features which normal Python
class inheritance doesn't have to deal with in quite the same way, so the
difference between Django model inheritance and Python class inheritance isn't
merely arbitrary.
arbitrary.
This restriction only applies to attributes which are
:class:`~django.db.models.fields.Field` instances. Normal Python attributes
@ -1229,4 +1229,3 @@ different database tables).
Django will raise a ``FieldError`` exception if you override any model field
in any ancestor model.