Skip to content

Conversation

jorgebg
Copy link
Contributor

@jorgebg jorgebg commented May 5, 2016

Due to the way Django Polymorphic sets the PolymorphicManager, we need to override their manager explicitly in order to make it work the way it is supposed to. I haven't found any other way of doing this.

What do you think?

Due to [the way](https://github.com/chrisglass/django_polymorphic/blob/master/polymorphic/base.py) Django Polymorphic sets the `PolymorphicManager, we need to override their manager explicitly in order to make it work the way it is [supposed to](https://github.com/edoburu/django-polymorphic-tree/blob/2439464/polymorphic_tree/models.py#L80). I haven't found any other way of doing this.

What do you think?
@vdboor
Copy link
Member

vdboor commented May 23, 2016

@jorgebg I'm not sure what to think of this issue. If polymorphic does things the wrong way, could that be fixed instead? That would help us avoiding workarounds on top.

While Django's way how it's "supposed to be" is preferred, the polymorphic approach might be needed to ensure polymorphic behavior works everywhere. Any help or insight here is highly appreciated.

@vdboor
Copy link
Member

vdboor commented Jan 11, 2017

This issue is fixed in 1.3

@vdboor vdboor closed this Jan 11, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants