Thanks for your comments BetterRed.
Quote:
Originally Posted by BetterRed
- did you try Library Maintenance->Restore database
|
I didn't do that ... and maybe it would have fixed the problem.
But as I was preparing to do that just now (after making a backup copy of the library), I tried a few bulk metadata edits as a benchmark for what to try after running the restore, and lo and behold the bulk edit process now seems to be working okay (without running the restore)!!
I don't get it. But for now the problem seems to have gone away. I wonder if the main metadata.db file has some sort of delayed self-correction as it continually updates itself ? I don't know at what point the problem went away because as I tried different things I kept testing to see if the bulk edit process was working. Then I ignored it and proceeded doing other work and work-arounds.
Quote:
Originally Posted by BetterRed
On occasions I've had to edit the metadata_db_prefs_backup.json file to get rid of the 'malformed' data
|
That step is probably beyond my skill level. I tried a quick internet search and didn't find much. With windows explorer I can see the file in the Calibre directory (very small 46kb compared to the much larger multi-MB metadata.db file) and I can open and read the unformatted data stream with a basic text editor, but wouldn't know how to determine what was malformed data. It also seems risky to do any direct editing of the file and it seems more like an output data stream rather than a structured input data stream.
But I digress from the main topic in this thread and, inexplicably, the problem appears to have gone away. Hopefully it will not return. : / ...THANK YOU.