diff options
| author | Carlton Gibson <carlton.gibson@noumenal.es> | 2021-06-09 16:55:22 +0200 |
|---|---|---|
| committer | Carlton Gibson <carlton.gibson@noumenal.es> | 2021-06-15 12:01:28 +0200 |
| commit | 225d96533a8e05debd402a2bfe566487cc27d95f (patch) | |
| tree | ccffbb958d84e8a2a7db9788af93a69ae36748d1 /docs | |
| parent | 0c0240aba8c769406248b5601126b891998fabb7 (diff) | |
Fixed #30427, Fixed #16176 -- Corrected setting descriptor in Field.contribute_to_class().
Co-authored-by: Jarek Glowacki <jarekwg@gmail.com>
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/topics/db/models.txt | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/docs/topics/db/models.txt b/docs/topics/db/models.txt index 26a6d7dc58..1c4e99817f 100644 --- a/docs/topics/db/models.txt +++ b/docs/topics/db/models.txt @@ -1457,6 +1457,13 @@ different database tables). Django will raise a :exc:`~django.core.exceptions.FieldError` if you override any model field in any ancestor model. +Note that because of the way fields are resolved during class definition, model +fields inherited from multiple abstract parent models are resolved in a strict +depth-first order. This contrasts with standard Python MRO, which is resolved +breadth-first in cases of diamond shaped inheritance. This difference only +affects complex model hierarchies, which (as per the advice above) you should +try to avoid. + Organizing models in a package ============================== |