Migration from FastAPI and role of SQLModel #3761
Unanswered
vikigenius
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I am migrating from FastAPI and I am reading the docs. I am specifically confused about DTO objects, SQLAlchemy and how they fit in.
SQLModel despite it's bugs and issues felt like I understood what was going on. It tried to unify Pydantic Models and SQLAlchemy model
and you can thus have a single
User
class that would handle both the DB side and the request/response validation side?Is that the purpose being served by something like
SQLAlchemyDTO
for example? In the https://github.com/litestar-org/litestar-fullstack example I see that you are still using two different User classes, one for the DB and one for the Response.Beta Was this translation helpful? Give feedback.
All reactions