Upgrade to psycopg3 from version 2 #201
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
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.
Ticket
#200
Changes
Upgraded psycopg, the library that connects to Postgres for SQLAlchemy, to version 3.
Context for reviewers
Version 2 was named
psycopg2but version 3 is justpsycopgso that they can upgrade without changing the package name moving forward.Changing the connection string to
postgresql+psycopgtells SQLAlchemy internally to use the new library: https://docs.sqlalchemy.org/en/20/dialects/postgresql.html#dialect-postgresql-psycopg-connectSince we only have a few direct interactions with psycopg, the changes were fairly minimal, just adjusting the DB connection info object slightly.
Testing
Migrations, unit tests, and other automations still running fine.
Was able to pull up swagger and read/write to the DB via our endpoints.