View Single Post
Old 10-26-2018, 10:36 PM   #22
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by DNSB View Post
Have you looked at the design of SQLite? Check this link for more information: How To Corrupt An SQLite Database File paying special attention to the first paragraph. Then read the rest to help give some basis to paranoia about database corruption.
Interesting. I feel like there have been less issues since Kobo change to write-ahead logging. I was also forced to change the SQLite library used to support this, so that might have helped as well. For Windows calibre users at least.

I'll have to think about some of the other things mentioned on that page. And workout exactly what SQLite versions are involved.

Last edited by davidfor; 10-26-2018 at 10:39 PM. Reason: Grammar.
davidfor is offline   Reply With Quote