add example error messages

website/docs/reference/resource-configs/constraints_enabled.md

@@ -15,12 +15,52 @@ You can manage data type constraints on your models using the `constraints_enabl
 You can configure `constraints_enabled` in `schema.yml` files to apply constraints one-by-one for specific dbt models in `yml` config blocks. You'll receive dynamic error messages if you do not configure constraints based on the criteria below.
 
 - Constraints must be defined in a `yml` schema configuration file like `schema.yml`.
+
 - Only the `SQL` **table** materialization is supported for constraints.
+
+```txt
+Parsing Error
+  Original File Path: (models/constraints_examples/constraints_example.sql)
+  Constraints must be defined in a `yml` schema configuration file like `schema.yml`.
+  Only the SQL table materialization is supported for constraints. 
+  `data_type` values must be defined for all columns and NOT be null or blank.
+      Materialization Error: {'materialization': 'snapshot'}
+```
+
 - `data_type` values must be defined for all columns and NOT be null or blank.
+
+```txt
+Parsing Error
+  Original File Path: (models/constraints_examples/constraints_example.sql)
+  Constraints must be defined in a `yml` schema configuration file like `schema.yml`.
+  Only the SQL table materialization is supported for constraints. 
+  `data_type` values must be defined for all columns and NOT be null or blank.
+      Columns with `data_type` Blank/Null Errors: {'id'}
+```
+
 - `constraints_enabled=true` can only be configured within `schema.yml` files NOT within a model file(ex: .sql, .py) or `dbt_project.yml`. *(Note: Current parsing mechanics require all constraints configs be written in schema files to be implemented exactly as configured. This may change in the future.)*
+
+```txt
+Parsing Error
+  Original File Path: (models/constraints_examples/constraints_example.sql)
+  Constraints must be defined in a `yml` schema configuration file like `schema.yml`.
+  Only the SQL table materialization is supported for constraints. 
+  `data_type` values must be defined for all columns and NOT be null or blank.
+      `constraints_enabled=true` can only be configured within `schema.yml` files
+        NOT within a model file(ex: .sql, .py) or `dbt_project.yml`.
+```
+
 - Please ensure the name, order, and number of columns in your `yml` file match the columns in your SQL file.
 
-> Note: constraints and data type inheritance across downstream tables depends on database-specific functionality. Bias towards defining constraints for all tables in scope where desired.
+```txt
+# example error message
+Compilation Error in model constraints_example (models/constraints_examples/constraints_example.sql)
+  Please ensure the name, order, and number of columns in your `yml` file match the columns in your SQL file.
+  Schema File Columns: ['ID', 'COLOR', 'DATE_DAY']
+  SQL File Columns: ['ERROR', 'COLOR', 'DATE_DAY'] 
+```
+
+> Note: constraints and data type inheritance across downstream tables depends on database-specific functionality. We recommend defining constraints for all tables in scope where desired.
 
 <Tabs
   defaultValue="models"