-
Notifications
You must be signed in to change notification settings - Fork 552
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
Incompatibility with SQLAlchemy 2.0.0+ #443
Comments
I've added a pull request to fix this: I'm not able to sign the CLA at the moment, so the pull won't get approved - but the changes are almost trivial - if you inspect the request you can see how it's done. |
Nice work! Although I suspect for complete compatibility there needs to be a fix in |
Could it be merged please ? |
This PR #448 includes the change and has been merged. But then got reverted here: df03bef @bkyryliuk what's the situation atm? |
I am working on a comprehensive PR to add SQLAlchemy 2.0 Support. Should be ready soon. |
PR raised #457 |
PR #457 is merged. |
@PApostol @james1465 @belgacea @glungley PyHive is now compatible with SQLAlchemy 2.0. See #457 |
I have tried PyHive 0.7.1.dev0 with SQLAlchemy 2.0.19, it appears to work fine! |
PyHive 0.7.0 is released which includes Python 3.11 and SQLAlchemy 2.0 support. |
SQLAlchemy 2.0.0 has been released on the 26th of January 2023, and it's incompatible with PyHive for connections to Presto, Trino and Hive:
Similarly,
and
Pinning
SQLAlchemy<2.0.0
resolves the issue.The text was updated successfully, but these errors were encountered: