Iaroslav Zeigerman

> The model reference was only replaced for the physical table that referenced the audit when using my environment. Other models were not substituted and therefor used the promoted views...

> it would be problematic again. Why though? Didn't setting the `depends_on` on the **model** for which the audit runs help?

Thanks for reporting @MikeWallis42! > By this point the view has already been modified to an Iceberg view and so Trino can't drop it when using the Hive catalog as...

Model kind changes should be categorized as `BREAKING` even if it's a forward-only plan.

This looks great, thank you! Any chance you can also update docs: https://github.com/TobikoData/sqlmesh/blob/main/docs/integrations/engines/duckdb.md and include an example there?

@Kayrnt, no, unfortunately, querying `INFORMATION_SCHEMA` is a big part of the existing evaluation flow. I agree that this change is still useful.

@hafenkran > However, I ran into issues during the initial setup of the [migrations](https://github.com/TobikoData/sqlmesh/tree/main/sqlmesh/migrations). Migrations are only relevant in the context of SQLMesh state and I believe nobody should ever...

@eakmanrq how would this work if a user restates a discontinued range? Eg. if today is Jan 20th, and the user restates Jan 10th - Jan 15th

@MikeWallis42 is the purpose of this to make the queries in logs prettier? Or some other place?

I'm concerned that this will significantly increase the size of the payload and the IO overhead as a result. I'm open to making this configurable with this behavior being disabled...