Reverse relation still exposes deleted objects

[decibyte]

I think I've found a bug, but it might be me doing something wrong.

Have a look at the test case project I created to show what the bug is.

I've created 2 simple models: Parent and Child. Child has a OneToOneField relation to Parent.

If I create one of each -- child relating to parent -- and then delete the child, then the child is still accessible via parent.child.

I would expect this to raise a DoesNotExist, as the child is (soft)deleted.

[natehawkboss]

Yes, I have the same issue. It is actually causing some problems for me as it was pulling up deleted records in a form and filling it out, but then obviously not explicitly un-deleting the record when it was saved, just updating the deleted record.

[adiTrullion]

Hey, any idea how to make it work?

[rizkyarlin]

I am currently working on a similar case. For me it's for checking if the children exists in a ReverseManyToOne. Still working on a PoC.

But for OneToOneField, I believe it's a little bit trickier.

For OneToOneField I'm thinking about doing something like:

overwriting the init() of django.db.models.base.Model

to do something like:

            if is_related_object:
              
                if rel_obj is not _DEFERRED:
                    if isinstance(rel_obj, SoftDeleteObject):
                        if rel_obj.deleted_at is not None:
                            raise ObjectDoesNotExist()
                    _setattr(self, field.name, rel_obj)