Upgrade sqlalchemy requirement to v2#160
Merged
paulf81 merged 2 commits intoNatLabRockies:developfrom Jan 24, 2024
Merged
Conversation
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
1 participant
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.
Upgrade sqlalchemy requirement to v2
This pull request addresses Issue #159. Previously there had been some errors when using sqlalchemy v2, but raising the requirement and testing the code for both reading and writing to postgres shows no issue so implementing this pull request to raise the requirement to ~=2.0. The pull request also fixes some small issues in sqldatabase_management.py identified in testing. Since this is a very small change, directly merging (hope that is ok @misi9170 !)