Quote:
Originally Posted by compurandom
That's very valid but you gotta get lucky! You have to eject and reboot before anything else especially calibre starts scribbling on the database.
|
As far as I can tell, as long as the message was on screen, calibre wasn't trying to write to the database. So as I said, close calibre immediately and eject the Kobo. I ran ~14 tests and did not get database corruption doing this. OTOH, it was simply easier to reboot my Kobo before connecting.
Quote:
Originally Posted by compurandom
Maybe the issue is that the kobo OS has the database open but the wal file only exists in cache memory and hasn't been written to disk yet, so the OS calibre is in doesn't see it.
|
From the documentation, the -wal and -shm files are written to disk and not stored in memory. The problem is that they have to be written to the database before the database is closed though the SQLite code seems to handle the database not being properly closed so the -wal and -shm files will be merged when the database is re-opened unless the database has been hooped in the meantime.