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 was archived by the owner on Aug 19, 2025. It is now read-only.
@tomchristie big news (if news)! sqlalchemy has now async engine that supports asyncio for Core and ORM, also it finally supports asyncpg as the driver.
While it's still considered to be an alpha, it's a huge step forward. It can also solve several classes of problems databases has. Like:
dependency on psycopg2 for alembic or initial DB DDL
subtle syntax differences in generated SQL that we observed (psycopg vs asyncpg)
ORM support
tighter migration and more unified usage of drivers (yet to be clarified how many async drivers are supported),
some other.
It seems to be quite a big change, so I am wondering if there any strategy or view around that. With async API maturing in sqlalchemy it might worth considering adapting databases either into tighter integration with sqlalchemy or decoupling sqlalchemy at all providing a thin API on top of raw drivers (in case bringing databases with sqlalchemy might seem redundant).
This discussion was converted from issue #245 on March 25, 2021 15:04.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
@tomchristie big news (if news)!
sqlalchemyhas now async engine that supports asyncio for Core and ORM, also it finally supportsasyncpgas the driver.While it's still considered to be an alpha, it's a huge step forward. It can also solve several classes of problems
databaseshas. Like:psycopg2for alembic or initial DB DDLsome other.
It seems to be quite a big change, so I am wondering if there any strategy or view around that. With async API maturing in
sqlalchemyit might worth considering adaptingdatabaseseither into tighter integration withsqlalchemyor decouplingsqlalchemyat all providing a thin API on top of raw drivers (in case bringingdatabaseswithsqlalchemymight seem redundant).Beta Was this translation helpful? Give feedback.
All reactions