Closed pomartel closed 3 years ago
This is more complicated than I first thought. Counter caches and permanent deletes also need to be handled correctly. I started implementing a custom DestroyAssociationAsyncJob
but now I see that the gem maintainers don't accept new features so I will close this PR for now but I would be interested in digging deeper if there is a chance this feature can be accepted.
@pomartel I am definitely interesting seeing destroy_async
support in paranoia
Sorry @mathieujobin, I opted to destroy records asynchronously in my own code instead (using a background job).
No problem
It sounds like a good solution
Fixes #507