handle related managers for custom through models

[makinacorpus]

handle related managers for custom through models

[ron8mcr]

Hi @smcoll.
I've implemented this for django 1.10 in PR #63. However, this works just for 1.10 and for <1.10 require overriding 2 classes. I do not have time to finish this now.

Also, my fix works just in your case. This code work incorrect:

> Foo.objects.filter(fobbar=bar).count()
1

I found fix for that in django-permanent (see related.py). But IMHO this is hacky way.

[smcoll]

Thanks @ron8mcr

[ddahan]

Any news on this issue? @ron8mcr @smcoll

I have a similar problem.

class Article(SafeDeleteModel):
   _safedelete_policy = SOFT_DELETE_CASCADE

class Category(SafeDeleteModel):
    _safedelete_policy = HARD_DELETE
    articles = models.ManyToManyField(Article, through='ArticlesByCategory', blank=True)

class ArticlesByCategory(SafeDeleteModel):
    _safedelete_policy = SOFT_DELETE
    article = models.ForeignKey(Article)
    category = models.ForeignKey(Category)

When running Article.objects.filter(articlesbycategory__category=category), all the ArticlesByCategory objects are used. I expect the manager to use only undeleted objects.

Any workaround? Thanks.