A shift to SQLAlchemy and more respect for FastAPI legacy? #1367
Closed
ManiMozaffar
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hey there,
I'm implementing a translation version of SQLAlchemy, using asyncpg to asynchronous the connections to db.
I wanted to first use this library, but there's many things wrong with it.
Why would you reproduce django ORM without respecting to fastapi's legacy?
A friend told me:
It'd have been perfect if we could use SQLAlchemy alongside with this ORM, so the problems with not supported query would have been solved for experts at least, and the juniors could have used library for simpler usage.
How would you do this query?
With my current version of ORM:
I know it's not the approach that django uses, because that approach can't handle such query, but it's still nice to have freedom to inject where or select to our queries.
Beta Was this translation helpful? Give feedback.
All reactions