Gagaro
Gagaro
I guess the easiest way for you to do that would be to have your own `SafeDeleteModel`, and using that one: ```python class CustomSafeDeleteModel(SafeDeleteModel): deleted = models.DateTimeField(name='deleted_at', editable=False, null=True) class...
Did you overwrite the manager of your model without inheriting from `SafeDeleteManager`?
`AbstractUser` has a custom manager. You should create your own manager which inherits from both `UserManager` and `SafeDeleteManager` and set it on your model.
Your manager needs to inherits from both `UserManager` (from `django.contrib.auth`) and `SafeDeleteManager`.
Hi, thanks for the report. I'm not sure what's up here, I'm not even sure we are counting the changed objects from the right queryset from looking at the code....
I'm not sure if this is possible to easily do. In the meantime, you can filter on the aggregate manually: ````python Property.objects.annotate(bc=Count('rooms', distinct=True, filter=Q(deleted__isnull=True)) ```
Thansk for the contribution. I'm not sure there's a better way to do that, but I'm afraid of all the implication it could have on existing code as well. I...
Hi, was it with the 1.1.0? Filtering was moved to the query itself to fix those kind of things.
It's probably because the through instance is deleted but not the related one. I'll try to see if I can find a quick fix,
So because `create_forward_many_to_many_manager()` create a new manager inheriting from our own and not the other way around, it seems complicated to fix this. I added a test which reproduce this...