View Single Post
Old 01-25-2025, 02:15 PM   #21
PeterT
Grand Sorcerer
PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.
 
Posts: 13,563
Karma: 79436716
Join Date: Nov 2007
Location: Toronto
Device: Libra H2O, Libra Colour
The database is not rewritten on reboot. If the corruption is too bad (no idea how bad it had to be) it is deleted and a new one is created with your being forced to do a reset up of the device.

The closest you can get to knowing from the device itself is subtle signs like the reading position not being retained across reboots.

Within calibre it is detected in two distinct locations. One is from within the kobo device driver when it attempts to open the database. This is the check you will see after the device has been connected. The other is if the Kobo Utilities plugin has been installed where it issues a "PRAGMA INTEGRITY_CHECK" to perform an integrity check of the database, it's internal structures and contents.

Sent from my Pixel 7a using Tapatalk
PeterT is offline   Reply With Quote