(WIP) Support for Postgres as an alternative backend to sqlite #136
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Parallel to issue #125
I've been working on supporting Postgresql as an alternative to sqlite as the backend for deployment at NTNU.
Things are mostly working, but I'm a little bit lost in fixing some outstanding aspects. This PR is not ready for merging, but I'm opening it to solicit some assistance in bringing the changes up to a standard to merge back in.
Changes so far:
clear_db
to delete child tables before parent tablesOutstanding issues:
pytest . --async-test-timeout 10
test_download_assignment
test_delete_assignment
test_download_submission
test_download_feedback
--no-upgrade-db
argument.test_ngshare.py
needs to be tidied up, but I've left that until I can figure the other issues out.