Florian Eiden

FYI, the PR is being finalized : https://github.com/dbt-labs/dbt-core/pull/5874

Thanks for opening the issue @adamcunnington-mlg As a conversation starter, what do you think of something like this: - freshness - loaded_at_location - `expression` : default, current behavior - `query`...

That's a good point. I'd rather we don't support `metadata` if the implementation is subpar. Do you have a specific vendor in mind for that comment, or is that more...

I like that Jeremy. A lot. But that will be a slow one. In the meantime, should we let users be clever for us at the table level? By that...

In terms of next step, we're projecting multiple [changes for sources for 1.6](https://github.com/dbt-labs/dbt-core/blob/main/docs/roadmap/2023-02-back-to-basics.md). I think that would be a great time to include this. But that means July. The adapters...

Hi @adamcunnington-mlg, we've been slipping on MVs, and I'm not 100% sure we're going to be able to fit the managed sources work into 1.6. I'm exploring alternative options to...

Hey @adamcunnington-mlg - sadly we didn't have the chance to take a stab at this, and I don't see us being able to in the near future. @dataders if you...

It's not unreasonable to scope that down to BQ only at the moment. We need to be pragmatic. @adamcunnington-mlg I understand you not wanting to waste cycles. I do think...

@adamcunnington-mlg I'm closing this as [solved in 1.7.3](https://github.com/dbt-labs/dbt-bigquery/issues/938). Let's open a follow-up issue if you think we can improve on the current implementation.

Is that what I want? Yes. Is that what's in the spec? [No](https://github.com/dbt-labs/dbt-core/issues/6911). Why is because there is no way for us to determine if the SQL has changed: -...