summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorSimon Charette <charette.s@gmail.com>2015-10-07 15:29:20 -0400
committerSimon Charette <charette.s@gmail.com>2015-10-12 12:14:27 -0400
commit5b980897f2da3c048d88029af554e0fc4be68a8e (patch)
tree8eae3580b0bfa8c48025b0f41ad9f1be6cf8c787 /docs
parent211486f3ab5602cdc332f03cd03fad3cb929d154 (diff)
Refs #18012 -- Made proxy and concrete model reverse fields consistent.
Prior to this change proxy models reverse fields didn't include the reverse fields pointing to their concrete model.
Diffstat (limited to 'docs')
-rw-r--r--docs/releases/1.10.txt9
1 files changed, 9 insertions, 0 deletions
diff --git a/docs/releases/1.10.txt b/docs/releases/1.10.txt
index 4868930bf8..1087c0bb55 100644
--- a/docs/releases/1.10.txt
+++ b/docs/releases/1.10.txt
@@ -238,6 +238,15 @@ But it didn't prohibit nested non-relation fields as it does now::
...
FieldError: Non-relational field given in select_related: 'name'
+``_meta.get_fields()`` returns consistent reverse fields for proxy models
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Before Django 1.10, the :meth:`~django.db.models.options.Options.get_fields`
+method returned different reverse fields when called on a proxy model compared
+to its proxied concrete class. This inconsistency was fixed by returning the
+full set of fields pointing to a concrete class or one of its proxies in both
+cases.
+
Miscellaneous
~~~~~~~~~~~~~