Hi roger, > > What you don't seem to understand is that your original database is corrupt. > The data that is in it is not exactly what SQLite (and hence your program) > put in it. While doing the dump, the corruption was discovered and the dump > aborted. You just replaced the abort > > command with "save what we have so > far". >
how to "replace" this? > > There is no way for SQLite to recover what is changed/missing/corrupted. > You'll need to work out what the damage has been. The integrity check only > examines the top level structure - it does not detect data changes (mostly). > For example if every 'a' had been changed to a 'b' it would not detect that. > > You should also work out how the corruption happened since you really don't > want it to happen again. Here is how to corrupt a SQLite database: > > http://www.sqlite.org/howtocorrupt.html > Hi roger , of course this is clear to me. But sometime my DB corrupted and .dump repairs it for me without data loose. (was only some index errors). But this time a part of the database goes really corrupt, so i now this data is lost. All I try with simon today is to create a new Db with the data that is not corrupted. The damage has come with a server blackout because USV failure. I now from docu that this can heavily damage a SQLite DB. Steffen _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
