Quote:
Originally Posted by BetterRed
I can't say if your idea will work, and I am not prepared to set up a scenario to test it - maybe someone else will be prepared to do that.
When someone's in a hole I don't throw them a spade to dig a deeper hole, I throw them line and haul them out of the hole. I've given you a solution for cleaning up 'libraries-in-an-dreadful-mess' that has been used to recovered 'messed up libraries' by many users in the past. That's all I am prepared to do.
BR
|
You dwell with wisdom and prudence.
For whatever reason, from beans to nuts, "Restore database" completed stage 3 but did not exit. The most recent "metadata.db" was apparently complete and intact. Calibre detects no errors. "metadata_pre_restore.db" seems to be a backup made by Calibre of Calibre Library's "metadata.db" when "Restore database" commences. In any case, it is very similar to the "metadata.db" included in the backup I made of the Calibre Library before thinning.
Killing Calibre processes and removing "metadata_pre_restore.db" and "metadata_db_prefs_backup.json" from the library caused no damage
in this specific scenario at the time I did it and with the system I used.
The method I proposed is unorthodox and I do not recommend anyone else attempt this.
It saved me a week or so, but I still do not know why Restore did not exit as expected - I'm low on disk space, I have a lot of Windows management services turned off and secpol restricts access to others and to various areas of my drive...it really could have been anything.
It worked...
this time...but thanks for taking the time to think about the issue and for your cautious advice.
Arro