For a trial of Klaxon, we added a page that would change often enough to trigger an alert for every page check. Now, we want to delete the page, but because it has so many snapshots, the deletion operation is timing out.
I believe this is a result of the slow cascading deletions noted in this blog post. It seems the authors have created a gem that nullifies the relationship between parent and child records (in this case page and page snapshots) and then destroys the child records asynchronously.
Given that the model relationships for Klaxon aren't too complicated, I'm wondering if another viable solution would be to delete instead of destroy the records. I'm not very Rails-savvy, so maybe that's a poor option.
Planning to give this gem a go and will open a PR if it works out for us.
For a trial of Klaxon, we added a page that would change often enough to trigger an alert for every page check. Now, we want to delete the page, but because it has so many snapshots, the deletion operation is timing out.
I believe this is a result of the slow cascading deletions noted in this blog post. It seems the authors have created a gem that nullifies the relationship between parent and child records (in this case page and page snapshots) and then destroys the child records asynchronously.
Given that the model relationships for Klaxon aren't too complicated, I'm wondering if another viable solution would be to
deleteinstead ofdestroythe records. I'm not very Rails-savvy, so maybe that's a poor option.Planning to give this gem a go and will open a PR if it works out for us.