Quote:
Originally Posted by DaveLessnau
It's odd that a repair will fix a newly-generated BookReader.sqlite file, but not fix one that's actually gone bad. At the very least, I'd think the repair process would see that the file is bad and just replace it on its own if it couldn't fix it with some minor edits.
|
I don't think it is odd at all. If it was easy to do that check, then that check should be done for the main database. And we don't know what is wrong with the file. It could be that the contents of the main database has been added to BookReader.sqlite but what should be in there is still there and valid. Or invalid in a way that appears to be valid. And when it is recreated, it will have default values which will probably trigger whatever is needed to populate the database correctly.
And I just opened a "bad" copy of BookReader.sqlite with a binary editor. Most of it is nulls. From that, it is could be just the file has been reallocated as a larger file and no bad data has been written to it. The size of the used part of the file appears to be about what I would expect it to be.