Quote:
Originally Posted by chaley
I wonder if I shouldn't change calibre to do both the scan and the load from metadata_db_prefs_backup.json. It isn't clear what to do with the results. My feeling is:
a) a column definition (a lookup key) found in metadata_db_prefs_backup.json should win over the same definition found in a metadata.opf, and
b) a column definition found in the scan that is not in metadata_db_prefs_backup.json should be added to the db.
This scheme could re-add old custom columns to the db, but that is easily fixed once the recovery finished. It would also deal with the problem you must have had, where the metadata_db_prefs_backup.json file was reinitialized somehow before the recovery was run.
|
First I have to say, I'm really happy that there IS a restore function!
Normally for people like me a crash is something new and you do what the manual is suggesting (you don't really know about what info is stored where and what will happen). So I think restoring too much columns would definitely be a lesser problem than restoring only the default columns.
And maybe there is a chance to save ALL custom columns (with templates and all). Like a back door, a file you can save somewhere else and load back in. Or is this function already there and I don't know about it?
Mini