From d7fa4fcbaf41f73441bff94fb9cfe534ab1474a1 Mon Sep 17 00:00:00 2001
From: Mike Gouline <1960272+gouline@users.noreply.github.com>
Date: Fri, 23 Feb 2024 15:12:38 +1100
Subject: [PATCH] Expand readme for column constraints (#235)

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index cb6e9a36..0c1ae5f2 100644
--- a/README.md
+++ b/README.md
@@ -93,7 +93,7 @@ Try running `dbt-metabase models --help` to see all the options available for fi
 
 ### Foreign Keys
 
-Built-in relationship tests are the recommended way of defining foreign keys, however you can alternatively use `fk_target_table` and `fk_target_field` meta fields. If both are set for a column, meta fields take precedence.
+Native [relationship tests](https://docs.getdbt.com/reference/resource-properties/data-tests#relationships) and [column-level constraints](https://docs.getdbt.com/reference/resource-properties/constraints#defining-constraints) are the recommended ways of defining foreign keys, however you can override them with `fk_target_table` and `fk_target_field` meta fields. If both are set for a column, meta fields take precedence.
 
 ```yaml
 - name: country_id