Reports in the 'saved_sql' don't hold sensitive information, and they're not large. It is entirely possible for staff members to accidentally delete reports, which then requires the reports to be restored from backups (assuming that a backup has even been made). If we could hide the reports rather than deleting them, that would make it easier to recover in this situation.
I am not sure about this one. Another idea: Make delete reports a separate permission.
BTW: If you activate syspref ReportsLog, deleted reports are logged including their SQL statment.
Good point, Marc! So actually we are already doing this in a way and it's optional.
I think the separate permission and the log both help to achieve this. Please reopen if you disagree.