Christophe Oudar

I have opened 2 PRs to fix the issue based on @takemikami blogpost (I just tweaked it to make it work with up to date version): - https://github.com/dbt-labs/dbt-core/pull/11386 - https://github.com/dbt-labs/dbt-adapters/pull/914...

Well it looks like a mandatory feature 😏 For the reviewers: - [the documentation about force install](https://duckdb.org/docs/extensions/working_with_extensions.html#force-installing-to-upgrade-extensions) - [the documentation regarding community extension installation](https://community-extensions.duckdb.org/index.html#how-to-use-a-community-extension)

Also pinging @hafenkran for visibility (probably something I'll try myself too when I find some free time!) Reading and writing to BigQuery in a single SQL file on SQLMesh while...

@izeigerman one problem that was identified is, apparently, [the way SQLMesh tries to access `INFORMATION_SCHEMA`](https://tobiko-data.slack.com/archives/C044BRE5W4S/p1728054728741209?thread_ts=1727966914.081469&cid=C044BRE5W4S) as BigQuery is mounted but AFAIK the DuckDB storage API doesn't support it yet. Do...

As there's no immediate workaround (maybe through a dedicated materialization like for project one). In the meantime, if you run into the issue, you can disable the related model by...

There's one approach I'm thinking of that you could leverage: environment variables. Then you can switch the region identifier using `DBT_BQ_MONITORING_REGION` ([see the doc](https://bqbooster.github.io/dbt-bigquery-monitoring/configuration/package-settings#environment)). Would it work for you?

Hello, thanks for reporting, I guess the schema from that field was updated and dbt... doesn't support automatic schema evolution on STRUCT. I'll make the update and try to find...

I had another thought about that problem: it didn't add a new field but it feels like Google updated the schema and the problem is that I can't really guard...

FYI I'm preparing a dbt bigquery change to support STRUCT field evolution. In the meantime 2 solutions for you: - full refresh the model (destroying the history) - updating manually...

Hello @eric-workweek, thanks for sharing! I'm not sure to know how I can help here but hopefully Google will fix it soon 🙏