Trey Spiller
Trey Spiller
Hi @MarcusKlik, Markdown documentation per column and for the whole tables would do exactly what I need. Great idea, and thanks so much for `fst`!
Agreed - thanks so much!
We do currently support reusable SQL macros written with jinja https://sqlmesh.readthedocs.io/en/stable/concepts/macros/jinja_macros/#user-defined-macro-functions
Yes, some info is still omitted: - "All model versions have been created successfully" - List of individual model times - "Evaluating models" - "All model batches have been executed...
Hi @ravenac95, thanks for sharing this. We'll have some internal discussions about how to move to a more efficient implementation.
Hi @ravenac95 - the updated implementation is about ready to go. https://github.com/TobikoData/sqlmesh/pull/3226 We would welcome any thoughts or feedback from your team!
Hello and thanks for the suggestion. Unfortunately, Fabric seems to have a [number of limitations relative to SQL Server](https://learn.microsoft.com/en-us/fabric/data-warehouse/tsql-surface-area#limitations), and some of those are used in core SQLMesh operations. If...
The limits on `ALTER TABLE ADD/ALTER/DROP COLUMN` were the main ones that concerned me. But you're right that those limitations would be feature-specific (primarily on forward-only), so there's no inherent...
Totally possible I'm misinterpreting that page - this text made me think it was platform-wide: ``` Applies to: ✅ SQL analytics endpoint and Warehouse in Microsoft Fabric This article covers...
Feedback addressed, also updated the MSSQL implementation to align