SQLAlchemy 2.0 support

[toinbis]

Hey there!

SQLAlchemy has already released a beta3 for 2.0, which would indicate the final 2.0 release is approaching quickly.

Currently sqlalchemy-bigquery support only <=1.4.27, if I am not mistaken. Am wonder is there a plan to support SQLAlchemy 2.0?

Thanks!

[tswast]

Thanks for the report! I think we're good now for 1.4.x versions, but I noticed in #513 that there are some failures we'll need to address for 2.x support. We'll keep this issue open while we figure out what's needed.

[Giuzzilla]

I think that a first step to go forward with this would be forcing the usage of SQLAlchemy >= 1.4 first (instead of >=1.2), this would allow using the new 2.0 syntax within the library (e.g. positional args in select statements vs iterables). https://docs.sqlalchemy.org/en/14/changelog/migration_20.html

[SlavaSkvortsov]

Hello!

Do you have any plans to unblock SQLAlchemy 2.0? It would be really helpful :)

Thank you!

[sar009]

Hi @tswast, SQLAlchemy 2.0 is out of beta now, can bigquery-sqlalchemy support 2.0

[meredithslota]

Hi folks — we don't have support for 2.0 planned yet, as there are some competing priorities internally. Apologies on the delays; we do not have an ETA yet for this.

[alexjironkin]

This is now a blocker for us to migrate to newer versions of both flask_sqlalchemy and sqlalchemy. When will you guys be able to look into supporting sqlalchemy v2? After all 1.4 is now a legacy version receiving minimal support.

[bpafoshizle]

Would be great to have this. This is preventing using langchain and llama-index for LLM development against big query as those require SQLAlchemy > 2.0. This means we may be pulling data out of BQ into e.g. postgres to build our LLM apps.

[richard-sparq]

@bpafoshizle 100% same here