> Yes. It's quite possible to have corruption which shows only when you hit a > particular row while using a particular index. The corruption can hide in > the file while you carry on adding rows or searching using other indices and > come to light only under some weird circumstance in the future.
It's even possible to have a corruption which wouldn't come to you as an error but just as a successful selection of malformed data. It happens when for some reason number of rows in the index is different from number of rows in the table. So in this case you will notice corruption only when you try to work with that malformed data. Pavel On Tue, Jun 8, 2010 at 11:02 AM, Simon Slavin <slav...@bigfraud.org> wrote: > > On 8 Jun 2010, at 3:39pm, Daniel Stutzbach wrote: > >> After talking with my user a bit more, he reported that he had a power >> outage around a week prior to the error. Is it possible that some part of >> the database became corrupt in a way that didn't immediately cause any >> problems? > > Yes. It's quite possible to have corruption which shows only when you hit a > particular row while using a particular index. The corruption can hide in > the file while you carry on adding rows or searching using other indices and > come to light only under some weird circumstance in the future. > > I'm not sure whether a power-cut at a particularly bad time could cause > something like this. The journaling mechanism built into SQLite should be > avoiding it, but your combination of PRAGMAs might be defeating the normal > defence mechanism. > > Simon. > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
