On Tue, Jan 10, 2017 at 11:29 PM, Clemens Ladisch <clem...@ladisch.de> wrote:
> Kevin O'Gorman wrote: > > If I go on to the second table, it appears to finish normally, but when I > > try to look at the database with sqlite3, a command-line tool for > > interacting with SQLite, it says the database is corrupt. > > What version? > It's whatever is in Python 3.5.2.'s builtin sqlite package. > > If however, I split the program into two programs, one for each table, > and > > run them one after another, all is well. Same code, each with parts of > it > > if-else-ed out. > > It's possible that there is a bug in your code. Which you have not shown. > > My opinion is that no user bug whatever should cause DB integrity problems without raising an exception. -- word of the year: *kakistocracy* _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
