<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/14020499f5f646b6bc80c909716850fd&quot; frameborder=&quot;0&quot; width=&quot;2560&quot; height=&quot;1920&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1920</height><width>2560</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1920</thumbnail_height><thumbnail_width>2560</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/14020499f5f646b6bc80c909716850fd-00001.gif</thumbnail_url><duration>504.93</duration><title>Column Type Constraints as dbt Native: Demo</title><description>Problem: When I have lots of dbt models, I want guarantees that schemas and constraints(think: not null columns) are enforced. But that&apos;s hard to do with current dbt functionality.

Short-term Solution: Custom database-specific macros to enforce column data types AND constraints AND default values. Theoretically, you may never need to run a not null test again.

Long-term Solution: Follow along the work in progress here-https://github.com/dbt-labs/dbt-core/issues/6079</description></oembed>