diff --git a/website/docs/reference/resource-properties/constraints.md b/website/docs/reference/resource-properties/constraints.md index 8a8e46f2fa3..bd0aaa65e20 100644 --- a/website/docs/reference/resource-properties/constraints.md +++ b/website/docs/reference/resource-properties/constraints.md @@ -36,6 +36,9 @@ models: constraints: - type: primary_key columns: [, , ...] + type: foreign_key # multi_column + columns: [, , ...] + expression: ". (, , ...)" - type: check columns: [, , ...] expression: " != " @@ -224,7 +227,7 @@ select - Snowflake constraints documentation: [here](https://docs.snowflake.com/en/sql-reference/constraints-overview.html) - Snowflake data types: [here](https://docs.snowflake.com/en/sql-reference/intro-summary-data-types.html) -Snowflake suppports four types of constraints: `unique`, `not null`, `primary key` and `foreign key`. +Snowflake suppports four types of constraints: `unique`, `not null`, `primary key`, and `foreign key`. It is important to note that only the `not null` (and the `not null` property of `primary key`) are actually checked today. The rest of the constraints are purely metadata, not verified when inserting data. @@ -434,7 +437,7 @@ Databricks allows you to define: - a `not null` constraint - and/or additional `check` constraints, with conditional expressions including one or more columns -As Databricks does not support transactions nor allows using `create or replace table` with a column schema, the table is first created without a schema and `alter` statements are then executed to add the different constraints. +As Databricks does not support transactions nor allows using `create or replace table` with a column schema, the table is first created without a schema, and `alter` statements are then executed to add the different constraints. This means that: