Autobackup before every update.
Should we put Dbautobackuper.dll to every Miranda set-up and ,ake PluginUpdater trigger database backup before every update? (We can distribute dbautobackup within PluginUpdater archive in addition to separate component. Will it be a welcome feature or user privacy violation (some users might not like being forced to backup their profile, even though they can disable db_autobackup in plugins).
Support for db_autobackups has been implemented.
-
Wishmaster commented
support for db_autobackups has been implemented.
-
Wishmaster commented
Robert, why can't PluginUpdater backup it on it's own? Is there any other argument then "ghazan activly refuses to implement backup in PluginUpdater"?
The checkbox "Backup profile before update" could use db_autobackups when it exists, otehrwise use it's own implementation.Because I wouldn't want to include db_autobackups in the default distribution archive.
Anyway, I could implement support for db_autobackups and/or own backup, just make a decision about that!
-
I think solution would be to add checkbox into PU's options: "Backup profile before update".
And it would require installed db_autobackups, as it will be using their service for backup. It should be enabled by default.
But question is whether to include db_autobackups in default distribution archive. (Not inside PU archive)
-
Wishmaster commented
I disagree with ghazan, but I also don't want to include db_autobackups into releases because it is overkill for such a small operation.
-
Vadim Dashevskiy commented
@Wishmaster ghazan activly refuses to implement backup in PluginUpdater - says it's not his job.
-
Wishmaster commented
I think including db_autobackups would be too much, but we can implement a simple backup function inside PluginUpdater itsself to backup just the last profile and overwrite it on each update. Would be quite simple, and no need for another plugin. How about that?