On 24 Mar 2014, at 12:10pm, Markus Schaber <m.scha...@codesys.com> wrote:
> Not agreed. Another way to solve this problem is to include the file offset > or sector number into the checksum - this will also detect "movements" of > data to the wrong place, without the need for an atomically writeable > "external" storage. Store the page number (or some equivalent) inside the page. Neat. Unfortunately it doesn't catch the situation where a SQLite page gets its sector changed to a sector outside the SQLite file -- to, perhaps to a sector which is currently not being used where corruption will never be noticed. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
