-
Notifications
You must be signed in to change notification settings - Fork 9
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
info_cache is now required for to_sql? #15
Comments
I got a response from sqlalchemy that it's Vertica responsibility to update dependencies. I see that there are similar issues there but Vertica developers don't bother to update the interface. The issues were raised a year ago. |
if you check the readme you will see sqlalchemy 2.0 is not supported, sqlalchemy>=1.3.24,<=1.4.44 |
Are there any plans supporting it
…On Mon, Mar 11, 2024 at 3:08 PM Nicolae Rosia ***@***.***> wrote:
if you check the readme you will see sqlalchemy 2.0 is not supported,
sqlalchemy>=1.3.24,<=1.4.44
—
Reply to this email directly, view it on GitHub
<#15 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AWUYS3A5VNOJCM2VV5QWC4LYXX6JRAVCNFSM6AAAAABEQVTXMSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOBZGIZTANJXG4>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
--
Please note that Lukka does *not* accept cryptographic material such as
keys or other sensitive information via e-mail. The content of this e-mail
is confidential and intended only for the use of the specified recipient.
If you are not the intended recipient, any review, dissemination,
distribution or copying of this e-mail is strictly prohibited. If you have
received this e-mail in error, please notify us immediately by reply and
immediately delete this message and any attachments. The integrity and
security of this e-mail cannot be guaranteed over the internet, please do
not reply with confidential information.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello, it looks like SQLAlchemy has changed requirements on the fly without consulting the DB vendors.
They call the dialect method has_table with extra parameter info_cache. But vertica-sqlalchemy-dialect doesn't expect this parameter. I was wondering if it's possible to add **kw dummy parameter to all the methods in base.py so that sqlalchemy doesn't fail?
I raised the issue with SQLAlchemy but obviously they blame it on Vertica. Here's the link:
sqlalchemy/sqlalchemy#11135
The text was updated successfully, but these errors were encountered: