Merge pull request
#2389 from takluyver/catch-histdb-errors...
Merge pull request
#2389 from takluyver/catch-histdb-errors
Catch sqlite DatabaseErrors in more places when reading the history database
It seems sqlite can encounter corruption and throw an error when reading the database, although it has connected successfully. This borrows the move-and-recreate machinery we already had on connecting to the database.
If such an error occurs, the corrupted file is moved and the user get warned of the name of the corrupted file.
