Repository navigation
dbt Constraints v1.0.11
What's Changed
- Fixed a SQL compilation error on Snowflake when the package updates RELY or NORELY on a constraint that already exists. Snowflake gives a constraint created without a name a generated name such as
SYS_CONSTRAINT_59eea5c2-a1d8-.... The package wrote that name without quotes, so Snowflake stopped at the first hyphen withsyntax error ... unexpected '-'. The package now quotes the name exactly as Snowflake stores it and escapes any quote characters inside it. Mixed-case constraint names now work too. If 1.0.9 or 1.0.10 failed for you with this error and kept you on 1.0.8, you can upgrade now. Credit goes to @b-per for finding the cause and providing the fix. Fixes #127 in #129 - Added integration tests for constraints with a Snowflake-generated name and with a mixed-case name.
- The integration tests now cover the newest versions dbt Projects on Snowflake supports, dbt Core 1.12.3 and dbt Fusion 2.0.0, plus dbt Fusion 2.0.8 run locally.
- The version in
dbt_project.ymland the README is now correct. The 1.0.10 release still listed 1.0.9 in both files.
Full Changelog: 1.0.10...1.0.11