-
Notifications
You must be signed in to change notification settings - Fork 125
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
[v5.1.0] Refactor the rest of the repositories to use sqlalchemy core 1.4 #632
Conversation
@cmyui should we do alembic stuff in this PR or another one? if the latter, i want to merge this into master |
also, i was thinking we could create a database adapter that wraps around |
I'm confident there are quite a few bugs in this so I'd like to diff against the generated alembic migrations first. I think a new |
Yup, that's a good idea. It seemed very error prone since |
00ff488
to
26046a2
Compare
sorry for the loaded commit - was unavoidable. latest commit adds a wrapper around databases as discussed above, and additionally ensures all of our queries are compatible with sqlalchemy 2.0 (all of the selects needed a slight syntax change) squashed quite a few bugs in the process; there were a couple random ones but the majority were the sqlalchemy statements being incorrectly passed to the database in the future i want to refactor the database wrapper to be strict and only accept |
6f9c5e1
to
1021f0a
Compare
Alright did my most thorough manual testing in a while on this PR & I think I've caught the major bugs. It still likely has some diffs in terms of the existing db schema vs. what this would generate, but I don't think anything major -- just things like incorrect |
Co-authored-by: James Wilson <tsunyoku@users.noreply.github.com>
…ible with sqlalchemy 2.0
ad3b049
to
0c42f72
Compare
Ty for your support on this PR @tsunyoku!! Much appreciated 🎉🎉🎉 |
Co-authored-by: James Wilson tsunyoku@users.noreply.github.com
Describe your changes
Related Issues / Projects
Resolves #394
Checklist