scoursen/django-softdelete — pull request #5 by volrath (2012-03-28 06:25:45+00:00)
Title: simple fix for issue #4

Simple fix for the issue #4, with tests.
I modified the test_app's models a little bit to test the behavior in many2many relationships.

I also think this is a simple monkeypatch to this problem, the real solution might be adding a "SoftDeleteForeignKey" (and "SoftDeleteManyToMany") that would create its own "SoftDeleteForeignRelatedObjectsDescriptor" (which creates the RelatedManager) when `contribute_to_related_class` is called, this way we could keep the api for multiple database support: using django.db.router to try and guess the db_for_read for the given instance, if any. I didn't implement this because I think there is a design decision required (and cause I got no time =)