You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 19, 2023. It is now read-only.
The project is currently tightly coupled to psycopg2. It should be decoupled and the business logic should depend on SqlAlchemy instead. This leads to:
unit tests can be written,
participants can depend on a versioned module for local calc of consistency and concordance.
Currently what many are doing is they copy-paste the methods into their project, since their models likely doesn't depend on postgres. Thus fixes/changes to this repo will not be synced to peoples models or 3rd-party tools.
Unit tests can't be written easily since psycopg2 is used directly. If SqlAlchemy is used an in-memory/sqlite driver can be chosen instead, without affecting the business logic.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The project is currently tightly coupled to psycopg2. It should be decoupled and the business logic should depend on SqlAlchemy instead. This leads to:
Currently what many are doing is they copy-paste the methods into their project, since their models likely doesn't depend on postgres. Thus fixes/changes to this repo will not be synced to peoples models or 3rd-party tools.
Unit tests can't be written easily since psycopg2 is used directly. If SqlAlchemy is used an in-memory/sqlite driver can be chosen instead, without affecting the business logic.
The text was updated successfully, but these errors were encountered: