-
-
Notifications
You must be signed in to change notification settings - Fork 89
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
Upgrade to SQLAlchemy 2.0 #1177
Comments
Just a heads up that the referenced pull request isn't moving forward very quickly and databases is short on maintainers — I'm the only one reviewing things right now and am not a user. If someone is interested in helping out on that pull request it may be appreciated! |
At long last the PR is merged! I'll start taking a look at integrating it on our end. It might also be worth looking at https://github.com/tarsil/databasez which is a more actively maintained fork |
Please, we need an urgent update at least temporary support to SQLAlchemy==1.4.52 I know you're working on SQLAlchemy 2 and Pydantic 2, but we need ORMAR to support SQLAlchemy 1.4.52 at least. I am receiving: Many external dependencies are waiting for this version and I'm stuck |
If you need something right now, you can install Ormar from my SQLAlchemy 2 branch https://github.com/pmdevita/ormar/tree/feature/sqlalchemy2 Everything should be working now and a number of dependencies are updated since the minimum version of Python has been increased to 3.8 |
@alexol91 as programmers, we must learn the dark arts of using workarounds :). In case you didn't know about these:
|
SQLAlchemy 2.0 brings full typing support, performance improvements, and some support for declarative model creation and dataclasses which might prove interesting. It also solves this security issue here https://pyup.io/v/51668/f17/ It would be ideal to upgrade to it to keep receiving support.
Currently, we need to wait on
databases
to add support for it, but it seems they have a mostly working PR here encode/databases#540I'd be willing to put in a PR for it once that's ready.
The text was updated successfully, but these errors were encountered: