Chris Baldwin
Chris Baldwin
Done - saw this has v1.1.1 milestone so updated changelog.md accordingly
A much simpler and less invasive solution to this specific issue would be to cast the issue away as per [freshness#loaded_at_field](https://docs.getdbt.com/reference/resource-properties/freshness#loaded_at_field) in the docs e.g. ````yaml loaded_at_field: CAST(updated_datetimeoffset_at AS datetime)...
FWIW, I'm getting the same `docker tag` failure with the [Azure DevOps task example](https://github.com/devcontainers/ci/blob/main/docs/multi-platform-builds.md#azure-devops-task-example)
+1 on disabling three-part names by default. If a statement includes references to objects that don't exist, Synapse will respond with "USE is not supported on this platform" instead of...
@prdpsvs let me know if you need anything else for this PR
Upstream cause: https://github.com/microsoft/dbt-synapse/pull/235 A quick local workaround is to create a `macros/get_limit_subquery_sql.sql` macro with the following: ```sql {# Synapse doesnt support ANSI LIMIT clause - instead set rowcount for the...
In our local projects we've just overridden this by lifting the [`alter_column_type`](https://github.com/dbt-msft/dbt-sqlserver/blob/f789ab0815b926bd68af6e901cd0e33b2895db3f/dbt/include/sqlserver/macros/adapters/columns.sql#L1-L18) macro from dbt-msft/dbt-sqlserver as we update to v1.7.x, as Synapse does support ALTER TABLE and sp_rename for columns:...