From 5b980897f2da3c048d88029af554e0fc4be68a8e Mon Sep 17 00:00:00 2001 From: Simon Charette Date: Wed, 7 Oct 2015 15:29:20 -0400 Subject: 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. --- docs/releases/1.10.txt | 9 +++++++++ 1 file changed, 9 insertions(+) (limited to 'docs') 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 ~~~~~~~~~~~~~ -- cgit v1.3