-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 21/03/14 15:24, Simon Slavin wrote: > Checksums stored with the page index lists,
SQLite already has the ability to carve out data on each page for other uses. For example the encryption extension uses this. > Nevertheless, the basic SQLite engine is so efficient that any > slow-down would be noticed and might cause complaints. It couldn't be on by default for backwards compatibility reasons. (WAL is another example of that.) So you don't have to use it. Those of us who would rather proactively know about data corruption (to the best of SQLite's ability to detect it) are happy to take whatever hit there would be. After all, fast queries on corrupted data are pointless. And as we see in messages on this list, finally spotting corruption long after it first happened is very hard to recover from and hard to nail down the cause for. Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.14 (GNU/Linux) iEYEARECAAYFAlMvwWMACgkQmOOfHg372QSnOQCdEpBWBvcNsntkZ6WPvDs0yAju fc0AoJzagj56DyoYrhmeE73rwHhe+D2f =ZAfw -----END PGP SIGNATURE----- _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
