Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update explanation of contract enforcement #4540

Merged
merged 4 commits into from
Dec 14, 2023
Merged

Update explanation of contract enforcement #4540

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
bc7c2f5
Update model-contracts.md
joellabes Nov 28, 2023
8a31700
Update website/docs/docs/collaborate/govern/model-contracts.md
mirnawong1 Nov 28, 2023
0154ccf
Merge branch 'current' into joellabes-patch-1
mirnawong1 Nov 28, 2023
592691a
Merge branch 'current' into joellabes-patch-1
matthewshaver Dec 14, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion website/docs/docs/collaborate/govern/model-contracts.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -91,7 +91,7 @@ When building a model with a defined contract, dbt will do two things differentl
Select the adapter-specific tab for more information on [constraint](/reference/resource-properties/constraints) support across platforms. Constraints fall into three categories based on support and platform enforcement:

- **Supported and enforced** — The model won't build if it violates the constraint.
- **Supported and not enforced** — The platform supports specifying the type of constraint, but a model can still build even if building the model violates the constraint. This constraint exists for metadata purposes only. This is common for modern cloud data warehouses and less common for legacy databases.
- **Supported and not enforced** — The platform supports specifying the type of constraint, but a model can still build even if building the model violates the constraint. This constraint exists for metadata purposes only. This approach is more typical in cloud data warehouses than in transactional databases, where strict rule enforcement is more common.
- **Not supported and not enforced** — You can't specify the type of constraint for the platform.


Expand Down
Loading