Switch dbt_constraints for dbt-core constraints #11
Comments
ataft
added a commit
that referenced
this issue
Jun 24, 2023
Support dbt 1.5+ and plan to switch to using dbt-core contraints (see note in readme) Note: dbt 1.5+ supports primary_key and foreign_key [constraints](https://docs.getdbt.com/reference/resource-properties/constraints). However, as of dbt-core v1.5.2, constraints require [contracts](https://docs.getdbt.com/reference/resource-configs/contract) to be enabled. The catch-22 is that contracts then require ALL model columns to define data_type, but data_type is database-specific, so you lose the incredible database agnostic features of dbt. For this reason, we use the [`dbt_constraints`](https://github.com/Snowflake-Labs/dbt_constraints) package to enable cross-database support for primary and foreign keys. The issue will be tracked [here](#11).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
dbt 1.5+ supports primary_key and foreign_key constraints. However, as of dbt-core v1.5.2, constraints require contracts to be enabled. The catch-22 is that contracts then require ALL model columns to define data_type, but data_type is database-specific, so you lose the incredible database agnostic features of dbt. For this reason, we use the
dbt_constraintspackage to enable cross-database support for primary and foreign keys.This issue has been raised in the following dbt-core discussion: dbt-labs/dbt-core#6726
The text was updated successfully, but these errors were encountered: