-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 06/02/12 09:11, Nico Williams wrote: > A checksum per-row is certainly a valuable thing at the layer above the > RDBMS since it allows for integrity checking above the RBDMS, and in an > RBDMS-independent manner.
It doesn't actually help that much since it is only over a portion of the database content. While it will catch an individual row being corrupted it will not catch the btree that points to the table rows being corrupted. If that container is "tweaked" then it could still be sufficiently valid but end up omitting the row so you will get wrong query results. The same story applies to indices where a judicious tweak will not corrupt it, but will result in the wrong rows being selected. Being able to integrity check the rows that are returned doesn't help if they are the wrong rows! It is nice that some filesystems are adding integrity protection (and in some cases recovery), but approximately zero percent of the systems out there running SQLite do not have the databases stored in such a configured filesystem today. Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk8wJ/YACgkQmOOfHg372QQ9AACgp1xLCbo9tEIqyF+Ar7ZqaKxi xjoAnjx6AEN0lP6ZP9QwVSKC642hpfao =wC3P -----END PGP SIGNATURE----- _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
