-
-
Notifications
You must be signed in to change notification settings - Fork 53
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
Add databases support with using async SQLAlchemy #46
Comments
@rszamszur why not use async sqlalchemy? SQLModel seems pretty good so we but I feel it's not really that mature yet and the releases are taking a lot of time. Also SQLAlchemy is kinda of a staple I feel like |
@jeanlst To be honest, I've initially chosen SQLModel since it combines pydantic and SQLAlchemy which is exactly what I wanted to do. Also since tiangolo has a lot of followers I assumed this project will gain a decent amount of contributors quickly, So I would end up implementing the same solution but heavily outnumbered 😆. Lastly, I guess I wanted to go the easy way. However, you're right in terms of maturity and release frequency. Also from what I've seen async session is not fully implemented, so no performance advantage (yet). Async SQLAlchemy it is then :) Thanks for the input! Have a good one! |
Nice! I'm keeping tabs on the project and you have been doing a great job so far! I'm still getting into all this stuff so I haven't been that helpful yet, bot hopefully in the future! |
@jeanlst just wanted to let you know, that this feature is next in line to implement. I don't know the ETA since there is some degree of unknown regarding how this will be implemented exactly. But this and few other issues combined will be a whole deal:
In the meantime controller and generator generators feature is already available with |
Feature Request
Draft implementation plan:
Core:
Generators:
Extra:
Documentation:
This still needs more research and clarification. Some implementation concepts might change during the development of this feature.
The text was updated successfully, but these errors were encountered: