From a270eef1fd3420e91a5a2516625f612b9a204229 Mon Sep 17 00:00:00 2001 From: Keryn Knight Date: Sat, 26 Oct 2013 15:53:15 +0100 Subject: [PATCH] Fixed #59 - manually setting the parent relation via a OneToOne should present the same behaviour as the implicit ptr Django generates on subclasses. Thanks to Eran Rundstein for reporting the issue and proposing the fix. --- model_utils/managers.py | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/model_utils/managers.py b/model_utils/managers.py index f0e34ee..9ac0317 100644 --- a/model_utils/managers.py +++ b/model_utils/managers.py @@ -110,8 +110,8 @@ class InheritanceQuerySet(QuerySet): if levels or levels is None: for subclass in self._get_subclasses_recurse( rel.field.model, levels=levels): - subclasses.append(rel.var_name + LOOKUP_SEP + subclass) - subclasses.append(rel.var_name) + subclasses.append(rel.get_accessor_name() + LOOKUP_SEP + subclass) + subclasses.append(rel.get_accessor_name()) return subclasses @@ -130,7 +130,7 @@ class InheritanceQuerySet(QuerySet): if levels: levels -= 1 while parent is not None: - ancestry.insert(0, parent.related.var_name) + ancestry.insert(0, parent.related.get_accessor_name()) if levels or levels is None: parent = parent.related.parent_model._meta.get_ancestor_link( self.model)