On 4 Jun 2018, at 6:32pm, Rael Bauer <supp...@bauerapps.com> wrote: > The last line in the dump using the latest version (3.23.1) is: > > ROLLBACK; -- due to errors
Then there are errors, and the data in your database may be corrupt, and the information you're getting from it can be wrong. Use the command-line tool to issue the command PRAGMA integrity_check; And give us some idea about what it reports. > Seems like a regression to me... The job of .dump is to reproduce the contents of the database. If the database is corrupt, .dump cannot do its job and it should certainly make sure that the user knows that. Why do you have so many corrupt databases that you've developed a system to reconstruct them ? Can you not correct the problem rather than losing data ? Depending on the way in which the database is corrupt, simply using VACUUM on it might be a better way to get rid of corruption. But depending on the type of corruption, VACUUM might lose even more data. You should investigate rather than just using it. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
