Suggestion: Backups before deleting tables
-
Hello.
I wanted to make a suggestion about the process of deleting tables in the database with your plugin.
From my point of view, it’s counterproductive to make a backup before deleting each table, especially when that deletion can’t be done in batches.
Suppose I uninstalled a plugin with 6 or 7 tables, which I have to delete one by one.
And that my configuration in Updraft-Plus saves the last 4 backups of the database.
So, if I made a copy before starting the deletion process, when I finish I will have 4 copies of which none contain all the deleted content.
Or I have to delete each backup created in each delete before starting the next one, unnecessarily lengthening the process.
I think that step should be optional. A recommendation notice that can be accepted or cancelled.
If I’ve already made my backup, I could cancel and keep my full one.
If I haven’t already done it, in the first delete, I can do it. Then it is no longer necessary.Even being able to configure the plugin settings to determine if a warning is displayed or a backup is started automatically.
Certainly something more flexible than what there is now, because the end result ends up being an incomplete database, which is just as bad as having no backup.
- The topic ‘Suggestion: Backups before deleting tables’ is closed to new replies.