06-05-2019, 01:27 AM
Is there any mileage in the installation process automatically making a backup of the existing database (I'm talking about the database without the underlying song files - I'm assuming they are less likely to be damaged)
Note: this is an emergency backup for installation purposes only - the user should still be making their own, full, backups
If this was possible, you could save an "emergency" backup to a name which includes the MS version i.e. you only create it if the file doesn't already exist. The logic should only keep the last 3 emergency backups i.e. files for older versions would be automatically purged. As a safety measure, it should probably avoid purge any files created within the last month (say)
You would obviously need to provide a mechanism to allow the user to recover from and/or or access an emergency backup.
Geoff
PS: I've turned automatic updating off several months ago and only update when it is convenient (and after using the companion to make a backup)
Note: this is an emergency backup for installation purposes only - the user should still be making their own, full, backups
If this was possible, you could save an "emergency" backup to a name which includes the MS version i.e. you only create it if the file doesn't already exist. The logic should only keep the last 3 emergency backups i.e. files for older versions would be automatically purged. As a safety measure, it should probably avoid purge any files created within the last month (say)
You would obviously need to provide a mechanism to allow the user to recover from and/or or access an emergency backup.
Geoff
PS: I've turned automatic updating off several months ago and only update when it is convenient (and after using the companion to make a backup)
Samsung Galaxy Tab A6