Skip to content

info_cache is now required for to_sql? #15

@leonidmakarovsky

Description

@leonidmakarovsky

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions