Quote:
Originally Posted by compurandom
I forgot about that -- it is possible for the in-memory copy of the database to be corrupt but the on disk version to be OK. In that case, restarting fixes it. I had that happen once.
|
Usually it is the other way round. The file is corrupt and changes can't be save. When it is reread during a restart, older and probably inconsistent data is read.
Quote:
|
If restarting doesn't fix it, then a wrong count is a sign of something deeper wrong in the database. Repairing indexes might fix it. If it doesn't, then short of a program to verify the semantics of the database vs. the the books on the device and all the books, not just the ones calibre knows about, you're going to have more problems later that are just easier to fix by rebuilding the database from scratch.
|
Repairing the indexes is unlikely to fix it. There isn't an index that could be causing this.
But yes, the sooner it is fixed the better. And if isn't, it will probably get worse and if the firmware can't read it at all, it will reset the database and prompt to be setup.