Closed pmareke closed 2 months ago
I've been reflecting on this for some time and, while the implementation of this PR is not bad, I think it is not solving the right problem in the right way.
The problem that we want to solve is twofold. On the one hand we want to remove old errors so they don't show in the dashboard or take space in the database. On the other hand we want to avoid recording errors based on some client-provided criteria.
Removing an error is not particularly useful as new occurrences will create that same error again. Furthermore, depending on the number of occurrences that the error has, the Repo.delete
operation may take a long time due to cascade deletions.
We are working on an error pruner that will remove old, resolved errors safely. But that requires careful consideration and measurement of query plans both in Postgres and SQLite.
So, thanks again for this work, but this is not a desirable feature at the moment.
This PR adds the possibility to delete a given error and emmits an event when the error is deleted.
Delete in the Dashboard view
Delete in the show view: