From 730820392fb3c79c42bdecc43bdc2cceaa63a390 Mon Sep 17 00:00:00 2001 From: ialdg <39755524+ialdg@users.noreply.github.com> Date: Wed, 27 Mar 2024 07:15:31 +0100 Subject: [PATCH 1/3] Update contract.md Hi. This proposal of modification is intended to keep the common praxis in all the examples present in your docs, that is, always attach a reference to the name of the file where the reader might find this particular instance of configuration. As a matter of fact, I copied and edited such reference from the example below the one I'm editing. Regards. IL --- website/docs/reference/resource-configs/contract.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/website/docs/reference/resource-configs/contract.md b/website/docs/reference/resource-configs/contract.md index 6c11b08dd62..3942d1f2f87 100644 --- a/website/docs/reference/resource-configs/contract.md +++ b/website/docs/reference/resource-configs/contract.md @@ -26,6 +26,8 @@ dbt uses built-in type aliasing for the `data_type` defined in your YAML. For ex Example for disabling: + + ```yml models: @@ -115,4 +117,4 @@ Why `append_new_columns`, rather than `sync_all_columns`? Because removing exist ## Related documentation - [What is a model contract?](/docs/collaborate/govern/model-contracts) - [Defining `columns`](/reference/resource-properties/columns) -- [Defining `constraints`](/reference/resource-properties/constraints) \ No newline at end of file +- [Defining `constraints`](/reference/resource-properties/constraints) From 66b214754c7c83331363a3c9fd93cac846663308 Mon Sep 17 00:00:00 2001 From: Mirna Wong <89008547+mirnawong1@users.noreply.github.com> Date: Wed, 27 Mar 2024 11:18:38 +0000 Subject: [PATCH 2/3] Update contract.md --- website/docs/reference/resource-configs/contract.md | 1 - 1 file changed, 1 deletion(-) diff --git a/website/docs/reference/resource-configs/contract.md b/website/docs/reference/resource-configs/contract.md index 3942d1f2f87..5bf88035712 100644 --- a/website/docs/reference/resource-configs/contract.md +++ b/website/docs/reference/resource-configs/contract.md @@ -38,7 +38,6 @@ models: alias_types: false # true by default ``` - When dbt compares data types, it will not compare granular details such as size, precision, or scale. We don't think you should sweat the difference between `varchar(256)` and `varchar(257)`, because it doesn't really affect the experience of downstream queriers. You can accomplish a more-precise assertion by [writing or using a custom test](/best-practices/writing-custom-generic-tests). From 1c9f53fc00ee9eabc863427b368f70a9231230ba Mon Sep 17 00:00:00 2001 From: Mirna Wong <89008547+mirnawong1@users.noreply.github.com> Date: Wed, 27 Mar 2024 11:21:35 +0000 Subject: [PATCH 3/3] Update contract.md add closer tag --- website/docs/reference/resource-configs/contract.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/website/docs/reference/resource-configs/contract.md b/website/docs/reference/resource-configs/contract.md index 5bf88035712..bf543f0eec9 100644 --- a/website/docs/reference/resource-configs/contract.md +++ b/website/docs/reference/resource-configs/contract.md @@ -38,6 +38,8 @@ models: alias_types: false # true by default ``` + + When dbt compares data types, it will not compare granular details such as size, precision, or scale. We don't think you should sweat the difference between `varchar(256)` and `varchar(257)`, because it doesn't really affect the experience of downstream queriers. You can accomplish a more-precise assertion by [writing or using a custom test](/best-practices/writing-custom-generic-tests).