View Single Post
Old 10-26-2018, 11:51 AM   #17
DNSB
Bibliophagist
DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.
 
DNSB's Avatar
 
Posts: 46,960
Karma: 169810634
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by johnnyb View Post
Because it's one big database in one file... If parts of the file get corrupted, everything tends to fall apart much quicker...
Are you suggesting that if they used separate database files, it would somehow be better? Gee, we only lost part of the information so it's all useless anyways.

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.
DNSB is offline   Reply With Quote