Skip to content

Commit

Permalink
Exsplcity state that a model contract enforces the column ordering
Browse files Browse the repository at this point in the history
Signed-off-by: Ash Smith <[email protected]>
  • Loading branch information
AshHimself authored Aug 2, 2024
1 parent 8994f8b commit eae40a1
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion website/docs/docs/collaborate/govern/model-contracts.md
Original file line number Diff line number Diff line change
Expand Up @@ -85,7 +85,7 @@ models:

When building a model with a defined contract, dbt will do two things differently:
1. dbt will run a "preflight" check to ensure that the model's query will return a set of columns with names and data types matching the ones you have defined. This check is agnostic to the order of columns specified in your model (SQL) or YAML spec.
2. dbt will include the column names, data types, and constraints in the DDL statements it submits to the data platform, which will be enforced while building or updating the model's table.
2. dbt will include the column names, data types, and constraints in the DDL statements it submits to the data platform, which will be enforced while building or updating the model's table, and order the columns per the contract instead of your DBT model.

## Platform constraint support

Expand Down

0 comments on commit eae40a1

Please sign in to comment.