did.database should be parallel / multithread friendly #59
Description
When running parallel processes, we get errors that "the database is locked". It's unclear what the right fix is.
- If sqlite3 has some sort of a multi-threaded option, it might be the best choice.
- Another fix would be to catch the error and have the program try again at random intervals every 1 second or so for up to 600 seconds, to attempt to complete its task. This might make it more common for a user to break the program (perhaps by control-C) while the program is in the middle of writing to its various tables, resulting in an incomplete entry. It is possible now but if the program spends more time waiting for access that isn't guaranteed to be instant, it might happen more often. Maybe we don't worry about this at the moment.