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 constraints.md #6053

Merged
merged 5 commits into from
Sep 13, 2024
Merged

Update constraints.md #6053

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
40ea3d5
Update constraints.md
diegoquintanav Sep 11, 2024
dfddbfc
Merge branch 'current' into patch-2
mirnawong1 Sep 12, 2024
f32abca
Update website/docs/reference/resource-properties/constraints.md
mirnawong1 Sep 12, 2024
9e68a5a
Update website/docs/reference/resource-properties/constraints.md
mirnawong1 Sep 13, 2024
599f112
Merge branch 'current' into patch-2
mirnawong1 Sep 13, 2024
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
10 changes: 10 additions & 0 deletions website/docs/reference/resource-properties/constraints.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,6 +23,14 @@ The structure of a constraint is:
- `name` (optional): Human-friendly name for this constraint. Supported by some data platforms.
- `columns` (model-level only): List of column names to apply the constraint over

<VersionBlock lastVersion="1.8">

When using `foreign_key`, you need to specify the referenced table's schema manually. Use `{{ target.schema }}` in the `expression` field to automatically pass the schema used by the target environment. Note that later versions of dbt will have more efficient ways of handling this.

For example: `expression: "{{ target.schema }}.customers(customer_id)"`

</VersionBlock>

<File name='models/schema.yml'>

```yml
Expand Down Expand Up @@ -62,6 +70,8 @@ models:

</File>



## Platform-specific support

In transactional databases, it is possible to define "constraints" on the allowed values of certain columns, stricter than just the data type of those values. For example, Postgres supports and enforces all the constraints in the ANSI SQL standard (`not null`, `unique`, `primary key`, `foreign key`), plus a flexible row-level `check` constraint that evaluates to a boolean expression.
Expand Down
Loading