From eae40a1722f3c95350c182853f82466605820516 Mon Sep 17 00:00:00 2001 From: Ash Smith Date: Fri, 2 Aug 2024 21:43:11 +0800 Subject: [PATCH] Exsplcity state that a model contract enforces the column ordering Signed-off-by: Ash Smith --- website/docs/docs/collaborate/govern/model-contracts.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/docs/collaborate/govern/model-contracts.md b/website/docs/docs/collaborate/govern/model-contracts.md index 80c4a4f9d81..bdd0cf63076 100644 --- a/website/docs/docs/collaborate/govern/model-contracts.md +++ b/website/docs/docs/collaborate/govern/model-contracts.md @@ -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