This pull request removes the sqlite database implementation, and cleans up the database test code so that the setup/teardown code is run automatically in each test case. See this doc for more details on the pytest config.
Now that we've settled on postgres, there is no need to continue to maintain the Sqlite implementation. It won't work anyway due to the need to store unbounded integers. If we want to reuse it later, we can always get the old implementation from the git history, so there is no reason to hold onto it. It is also getting in the way now that we're planning to make drastic changes to the database interface.
This pull request removes the sqlite database implementation, and cleans up the database test code so that the setup/teardown code is run automatically in each test case. See this doc for more details on the pytest config.
Now that we've settled on postgres, there is no need to continue to maintain the Sqlite implementation. It won't work anyway due to the need to store unbounded integers. If we want to reuse it later, we can always get the old implementation from the git history, so there is no reason to hold onto it. It is also getting in the way now that we're planning to make drastic changes to the database interface.