Skip to content

Tag: dbt

What is the value of schema tests in dbt?

When would you want to use a dbt schema tests (unique, not_null, accepted_values, & relationships) when you could instead use SQL schema constraints? For example, here are some SQL schema constraints that could replace each of the dbt schema tests: unique: UNIQUE constraint not_null: NOT NULL constraint accepted_values: FOREIGN KEY constraint to a lookup table relationships: FOREIGN KEY constraint to

Checking for different columns OR empty result PostgreSQL

I’m writing some query tests for dbt and I’d like to check that two queries return the same thing and that neither is empty. Since it’s a dbt test, I need to return a row if either of these conditions is false. So far I’ve come up with the following: Theoretically, this should return a row with 1 if either

How to add a Jinja function to .sqlfluff config

I’m using the jinja functions run_query and execute. But when sqlfluff lint I get the following error: Undefined jinja template variable: ‘run_query’ I’m trying to add it to the .sqlfluff config but there doesn’t seem to be any guidance anywhere on how to add this to the config file. Any help would be greatly appreciated! Thanks Answer Add templater=dbt

calculation with undefined number of rows

I would like to add a calculation taking into account we could have one, two, three or a lot of more rows. We can get all the data using the relations but I am a bit stuck because the number of relation are undefined. For example, as a source: Source Table id amount debt relation rn 123 250 225 NULL