On 21 Mar 2014, at 7:57pm, Roger Binns <rog...@rogerbinns.com> wrote:
> 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. There are problems with the particular formulation of checksums described in that ticket. It will miss corruption caused the majority of faults which will corrupt a database. Checksums stored with the page index lists, and then a checksum (of checksums ?) across the whole table or index would be an improvement, and would involve the minimum slow-down caused by the additional work and storage required. Nevertheless, the basic SQLite engine is so efficient that any slow-down would be noticed and might cause complaints. I suspect that the transition to SQLite4 is the first practical chance to introduce checksums. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
