35 migrate to mysql#43
Merged
Merged
Conversation
…truction240/discordqueuebot into 35-migrate-to-mysql
Closed
Closed
mewilker
approved these changes
Jul 8, 2026
mewilker
left a comment
mewilker
left a comment
Contributor
There was a problem hiding this comment.
You may want to implement the config table similar to how the autograder does if you forsee more configurable values in the future.
add rsa to support external database connections
mewilker
approved these changes
Jul 8, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Resolves #35 , Resolves #42
Moved away from the SQLite database used to store data and into the same MySQL server used by the autograder.
As far as I know, using a different "database" name will prevent conflicts with table names but I would appreciate fact checking on that one.
Also feel free to test this one out, I tried to test as much as I could for this since it's quite a big change, but I could have missed something. the new /setup command from my previous PR will make manual testing far easier.
Any suggestions to database schema/table definitions (found in db_manager.py) would also be appreciated so that future changes to the tables are minimal.
I included my work on #42 because an external database introduces greater latency, so some operations are beginning to take long enough to conflict with discord's response limitations