Can't restore from backup without "hacking" things

[Suedkiez (Just a fellow user like you)]

@Dirk_De_Taey

I just wanted to verify once more that what you are stating here is 100% correct?

There was definitely this:

@vova

Improved database integrity monitoring

Database corruption means that the records Roon is reading out of your database are different from what was originally written. This is uncommon and can happen for a variety of reasons, including failing hard drives. In some cases, corrupt records can remain in the user’s database undetected for some time, only being detected when an update ships that requires Roon to scan every record in the database.

These updates occur infrequently, which increases the risk of data loss – if the user has opted to only keep a few weeks of backups, the chances they have a usable backup drop significantly if the “latent” corruption isn’t detected for many months.

Starting in this release, we will be detecting database integrity issues “on the fly” – if corruption is detected during a backup, or during normal use of Roon, the application will halt and the user will need to restore from a backup.

As stated there, a database can be valid at backup time and still be corrupted later due to hardware issues. Plus, of course there is never a “100%” because bugs can happen and a corruption not be detected. I seem to recall that there was one other fix after build 880 that resolved one such issue, but I can’t find it now. I don’t think anyone did a formal mathematical proof that no other such bugs exist (because this would be unreasonable)