Anders

``` The col_3 column has differing values: expected_dictionary[col_3][2] == None actual_dictionary[col_3][2] == False ```

for some reason `sqlserver__dateadd` works on Azure SQL, but on Synapse, it comes up short by a day. | actual | expected | |-----------------------------|----------------------------| | 1900-01-02 00 00 00.0000000 |...

[dbt_utils.get_url_parameter()](https://github.com/dbt-labs/dbt-utils/blob/cd4c5e29006c8426ed8ae7b693ffb6966b14a08b/macros/web/get_url_parameter.sql#L5-L13) doesn't work currently (neither does `get_url_host` or `get_url_path`). I think it has to do with `dbt_utils.split_part`: https://github.com/dbt-msft/tsql-utils/blob/23b11b7e209c6d91dcb539316fb6c09f32fd1e01/macros/dbt_utils/cross_db_utils/split_part.sql#L5-L9 dbt-utils's integration test message is: > ('42000', '[42000] [Microsoft][ODBC Driver 17 for...

testing macros defined using CTEs

1

as I work on #59, I've had to disable ~17 tests in `integration_tests/dbt_utils/dbt_project.yml` for the same reason. The reason why is because of the pivot to the `test` block where...

Now that #38 is merged, the fun can begin, shimming macros to get the [dbt-expectations integration tests](https://github.com/calogica/dbt-expectations/blob/main/integration_tests/models/schema_tests/schema.yml) passing.

communicte what macros are not supported by tsql-utils

3

currently the only place where you can see what models are not supported is by looking at `integration_tests/dbt_utils/dbt_project.yml` (see below) which is not intuitive, but while the YAML is precise...

Port test_mutually_exclusive_ranges() to TSQL

1

my priority for this macro is not the macro itself, but really because it is used in `dbt-utils`'s integration testing for validation of OTHER macros. ### `calc` CTE [these two...

## problem statement I'm making a plugin to a python package that uses `agate` (namely: https://github.com/dbt-labs/dbt). The maintainers have made it to easy to plug in functionality after the csv...

remove postgres-only code

1

when querying `pg_views`, redshift coerces materialized views to be of `relkind='v'`, so the below case statement is not relevant to Redshift at all. I wish that Redshift wouldn't do this,...

## Description resolves: #173 ## Motivation and Context ## Testing ## Screenshots (if appropriate) ## Types of changes - [ ] Bug fix (non-breaking change which fixes an issue) -...