Reputation: 1064
When would you want to use a dbt schema tests (unique
, not_null
, accepted_values
, & relationships
) when you could instead use SQL schema constraints?
For example, here are some SQL schema constraints that could replace each of the dbt schema tests:
unique
: UNIQUE
constraintnot_null
: NOT NULL
constraintaccepted_values
: FOREIGN KEY
constraint to a lookup tablerelationships
: FOREIGN KEY
constraint to another tableUpvotes: 1
Views: 977
Reputation: 261
dbt tests are more flexible than database constraints. If you try to insert a null value to a not null target your process will fail, end of story. With dbt tests you can execute first, test after, which might be interesting.
More examples:
Upvotes: 4
Reputation: 3961
You can't have the above-listed table constraints on a view, or a CTE. The value of dbt is that users are allowed to build a DAG of SELECT
queries without having to worry about DDL or configuration. At a later point of time they can be configured to be tables instead of the default view, and no syntax need be changed.
Upvotes: 3