Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Changed session backend to use SQLAlchemy #18

Merged
merged 2 commits into from
Jul 21, 2022
Merged

Conversation

BryceStevenWilley
Copy link
Contributor

In anticipation of scaling better with thousands of feedback items.
The only significant change is to change the GUID to a normal, incrementing SQL int id. GUID isn't a SQL standard thing (only a postgres thing), and tbh we don't get too much from it, so the flexibility of working with other dbs is probably better than keeping it.

Fixes #14.

Copy link
Member

@nonprofittechy nonprofittechy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice--glad you were able to add this so quickly.

Since this is the refactor PR
@BryceStevenWilley
Copy link
Contributor Author

Final test that things worked. I also named some of the functions to better reflect they're about general feedback (not only session-tied feedback), and separated out the on-server feedback functions from the github ones, should have done that from the beginning.

@BryceStevenWilley BryceStevenWilley merged commit 39c7535 into main Jul 21, 2022
@BryceStevenWilley BryceStevenWilley deleted the sql_feedback branch July 21, 2022 20:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Switch to using SQL DB for the on-server feedback, not Redis
2 participants