-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 20/03/14 18:06, Simon Slavin wrote: > All useful as far as SQLite itself goes, and better than nothing. > Unfortunately, failing hard disks do weird things in weird orders. And > the interaction between the physical hard disk and the on-board cache > makes it impossible to find out what's really on the disk. There's > only one way to check whether the whole file is readable from a disk: > read the whole file from the disk. Then do an integrity check on the > copy you just made.
It also doesn't check the data, just the structure of the data. There was a feature request ticket for several years for checksums to at least catch unexpected changes to the data itself: https://www.sqlite.org/src/tktview?name=72b01a982a Sadly it was rejected a few weeks ago without explanation. Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.14 (GNU/Linux) iEYEARECAAYFAlMsmbQACgkQmOOfHg372QQy5gCfVa599WN9XWUB1Q8ABKYPJmQ6 QBwAnjuHzmK2oGfnhHDqdjlhD/5CoYe/ =1Y2C -----END PGP SIGNATURE----- _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
