You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 the models and tests in the integration tests don't necessarily correspond 1-1 with individual macros.
Maybe something in the README.md? Or perhaps just one issue per macro? However, dbt_utils.group_by() I know we'll never support. worth mentioning?
currently unsupported
after #17 the current macros we still could port are: test_split_part() (not working on Synapse?) test_date_spine() insert_by_period materialization generate_series() get_column_values() get_relations_by_pattern() get_relations_by_prefix_and_union() get_url_host() get_url_parameter() get_url_path()
perhaps for all the unsupported macros, we could implement sqlserver__* versions as wrappers for UnsupportedExceptions. @jtcohen6 I remember seeing an example of this somewhere but can't remember now...
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 the models and tests in the integration tests don't necessarily correspond 1-1 with individual macros.Maybe something in the
README.md
? Or perhaps just one issue per macro? However,dbt_utils.group_by()
I know we'll never support. worth mentioning?currently unsupported
after #17 the current macros we still could port are:
test_split_part()
(not working on Synapse?)test_date_spine()
insert_by_period
materializationgenerate_series()
get_column_values()
get_relations_by_pattern()
get_relations_by_prefix_and_union()
get_url_host()
get_url_parameter()
get_url_path()
tsql-utils/integration_tests/dbt_utils/dbt_project.yml
Lines 22 to 62 in b68b3a9
The text was updated successfully, but these errors were encountered: