Do you have a repeatable way to corrupt the database using the command line tool? We'd like to fix the main problem rather than fix a workaround.
What are the signs of database corruption? Error messages, weird results, output of pragma integrity_check, etc? Do you have a sample corrupted database you're willing to share? .dump exports the table contents out as SQL commands. So if that worked then the problems might just be in indexes, and running reindex might be a better workaround in the meantime. -----Original Message----- From: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] On Behalf Of Rael Bauer Sent: Monday, June 04, 2018 1:33 PM To: sqlite-users@mailinglists.sqlite.org Subject: Re: [sqlite] Repair corrupt database results in 0KB file @Simon: I did not mention any sqlite3.dll. I am only talking about sqlite3.exe command line tool. The problem occurs using the command line. Yes, I tried your idea. The last line in the dump using the old version is: COMMIT; The last line in the dump using the latest version (3.23.1) is: ROLLBACK; -- due to errors If I edit this to "COMMIT;", then it works ok if I read the dump file into a new database. Seems like a regression to me... -Rael _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
