Steven C. Gonzalez comments

Results 7 comments of


                                            Steven C. Gonzalez

`check-script-has-no-table-name` fails incorrectly due to `EXTRACT` function

@nasseredine -- I ran into this to and replaced `EXTRACT` with `DATE_PART` instead as a temporary fix.

Initial build fails with column size errors

I'm also running into this error, and made a work-around by changing the `dbt.type_string()` calls to `dbt.type_large_string()` in models `base_node_columns` and `base_source_columns` edit: I'm running dbt `v1.8` in Redshift with...

`dbt deps` and `dbt parse` succeeding with error code

Thanks @BAntonellini ! I tried the suggestion of removing the `environment` flag, but that didn't seem to work. What _does_ seem to be working is bumping to `dbt_version: 1.8.3` --...

`dbt deps` and `dbt parse` succeeding with error code

Thanks for the help, and thanks for the package!

Error in `base_source_columns` and `base_node_columns` in Redshift

Thank you! This issue has been resolved.

Fix `base_source_columns` and `base_node_columns` in Redshift

Hey @b-per For some reason, `dbt.type_string()` is creating `character varying(1)` columns, so this is causing the majority of the issues in these models (also reported in #463) However, I'm still...

Fix `base_source_columns` and `base_node_columns` in Redshift

Hey @b-per , here are the results from the `jq` command: ``` { "name": "type_string", "resource_type": "macro", "package_name": "dbt", "path": "macros/utils/data_types.sql", "original_file_path": "macros/utils/data_types.sql", "unique_id": "macro.dbt.type_string", "macro_sql": "\n\n{%- macro type_string() -%}\n...