-
Notifications
You must be signed in to change notification settings - Fork 27
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
[WIP] Switched to use SQLAlchemy (with Alembic for DB migrations) instead of plain psycopg2 #54
Conversation
@@ -1,48 +1,43 @@ | |||
from typing import Dict | |||
# TODO: Remove this file. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We will defintly not remove this file
import psycopg2 | ||
|
||
|
||
class DBConnection: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Alchemy can not appear anywhere else apart from this file. The whole applicaiton should not care about what DB client we are using.
I don't like using Alchemy in the applicatoin. It should be used only for DB migration.
I HATE ORM in general. It is a absolutly unnecessary complexity for any application.
I suggest you completly remove Alchemy. You only added unnecessary complexity to the project without any benefit
On request of @apssouza22 NOT to use an ORM, closing this PR. |
Not tested at all!
This PR is based on PR #52.