Skip to content
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

Open
leonidmakarovsky opened this issue Mar 11, 2024 · 3 comments
Open

info_cache is now required for to_sql? #15

leonidmakarovsky opened this issue Mar 11, 2024 · 3 comments

Comments

@leonidmakarovsky
Copy link

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

@leonidmakarovsky
Copy link
Author

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.

@nicolaerosia
Copy link

if you check the readme you will see sqlalchemy 2.0 is not supported,

sqlalchemy>=1.3.24,<=1.4.44

@leonidmakarovsky
Copy link
Author

leonidmakarovsky commented Mar 11, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants