On Wed, Jan 28, 2015 at 4:19 PM, Richard Hipp <d...@sqlite.org> wrote:
> On 1/28/15, Mario M. Westphal <m...@mwlabs.de> wrote: > > Recently I get an increasing number of error reports about “database disk > > image malformed” errors from my users. These errors show up out of the > blue, > > with databases held on local hard disks or even SSD’s, no power failures, > > Windows crashes or anything that’s in the rule book of “How to damage > your > > SQLite database”. > > > > This shouldn't happen. (But read > https://www.sqlite.org/howtocorrupt.html for more information). > To paste in part of a recent thread from the Fossil list which _might_ be relevant here... On Sat, Jan 24, 2015 at 10:10 PM, Richard Hipp <d...@sqlite.org> wrote: > On 1/24/15, Richard Hipp <d...@sqlite.org> wrote: > > On 1/24/15, Michai Ramakers <m.ramak...@gmail.com> wrote: > ...>> SQLITE_CORRUPT: database corruption at line 53682 of [1412fcc480] > > > > Actually, Fossil version 331204dc93 contained a dodgy version of > SQLite which could generate corruption reports such as the above. The > database was not really corrupt. The error was in the corruption > detection mechanism. That error has long since been fixed. -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal "Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do." -- Bigby Wolf _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
