Variables and control flow in dbt

Introduction

Variables store values you want to reuse. Control flow helps decide what code runs based on conditions.

You want to reuse a value like a date or a table name in multiple places.

You want to run different SQL code depending on a condition, like environment or user input.

You want to loop over a list of items to create multiple similar models or tests.

You want to make your dbt project flexible and easier to maintain.

Syntax

dbt

{% set variable_name = value %}

{% if condition %}
  -- code to run if true
{% elif other_condition %}
  -- code to run if other condition true
{% else %}
  -- code to run if none above
{% endif %}

{% for item in list %}
  -- code to repeat for each item
{% endfor %}

Variables are set with {% set %} and can hold strings, numbers, or lists.

Control flow uses {% if %}, {% elif %}, {% else %}, and {% for %} blocks.

Examples

Set a variable start_date and use it inside SQL with double curly braces.

dbt

{% set start_date = '2024-01-01' %}

select * from orders where order_date >= '{{ start_date }}'

Run different SQL depending on the environment (prod or dev).

dbt

{% if target.name == 'prod' %}
  select * from prod_table
{% else %}
  select * from dev_table
{% endif %}

Loop over a list of table names and run a count query for each.

dbt

{% set tables = ['customers', 'orders', 'products'] %}

{% for table in tables %}
  select count(*) from {{ table }};
{% endfor %}

Sample Program

This example sets a variable env to the current environment. Then it chooses the table name based on the environment. Finally, it selects data from the chosen table.

dbt

{% set env = target.name %}

{% if env == 'prod' %}
  {% set table_name = 'sales_prod' %}
{% else %}
  {% set table_name = 'sales_dev' %}
{% endif %}

select * from {{ table_name }} where sale_date >= '2024-01-01';

Important Notes

Remember to use double curly braces {{ }} to insert variables inside SQL code.

Control flow blocks must be properly closed with {% endif %} or {% endfor %}.

Variables and control flow help make your dbt models dynamic and reusable.

Summary

Variables store reusable values in dbt using {% set %}.

Control flow lets you run different code with {% if %} and loops with {% for %}.

Use variables and control flow to make your dbt projects flexible and easier to maintain.

Practice

1. What does the {% set %} statement do in dbt?

easy

A. It deletes a table from the database.

B. It runs a SQL query directly.

C. It defines a new model in dbt.

D. It creates a variable to store a value for reuse.

Solution

1. Step 1: Understand the purpose of {% set %}

   The {% set %} statement in dbt is used to create a variable that holds a value.

2. Step 2: Identify its use in code reuse

   This variable can then be reused multiple times in your dbt project, making code cleaner and easier to maintain.

3. Final Answer:

   It creates a variable to store a value for reuse. -> Option D

4. Quick Check:

   {% set %} creates variables [OK]

Hint: Remember: {% set %} means 'store this value' [OK]

Common Mistakes:

• Thinking {% set %} runs SQL directly
• Confusing it with model creation
• Assuming it deletes data

2. Which of the following is the correct syntax to create a variable named my_var with value 10 in dbt?

easy

A. {% set my_var = 10 %}

B. {% var my_var = 10 %}

C. {{ set my_var = 10 }}

D. {% set 'my_var' = 10 %}

Solution

1. Step 1: Recall dbt variable syntax

   In dbt, variables are created using the Jinja syntax: {% set variable_name = value %}.

2. Step 2: Check each option

   {% set my_var = 10 %} matches the correct syntax exactly. Options B and C use wrong keywords or delimiters. {% set 'my_var' = 10 %} incorrectly quotes the variable name.

3. Final Answer:

   {% set my_var = 10 %} -> Option A

4. Quick Check:

   Correct variable syntax uses {% set %} [OK]

Hint: Use {% set var = value %} without quotes around var [OK]

Common Mistakes:

• Using {{ }} instead of {% %} for setting variables
• Quoting variable names incorrectly
• Using wrong keywords like var

3. Given the following dbt code snippet, what will be the output of {{ greeting }}?

{% set hour = 15 %}
{% if hour < 12 %}
  {% set greeting = 'Good morning' %}
{% elif hour < 18 %}
  {% set greeting = 'Good afternoon' %}
{% else %}
  {% set greeting = 'Good evening' %}
{% endif %}
{{ greeting }}

medium

A. Good morning

B. Good evening

C. Good afternoon

D. No output (error)

Solution

1. Step 1: Evaluate the value of hour

   The variable hour is set to 15.

2. Step 2: Check the if-elif-else conditions

   Since 15 is not less than 12, the first condition fails. It is less than 18, so the second condition is true, setting greeting to 'Good afternoon'.

3. Final Answer:

   Good afternoon -> Option C

4. Quick Check:

   15 < 18 -> 'Good afternoon' [OK]

Hint: Check conditions in order; first true branch runs [OK]

Common Mistakes:

• Assuming hour 15 is morning
• Ignoring elif and jumping to else
• Thinking variable is undefined

4. Identify the error in this dbt snippet:

{% set total = 0 %}
{% for i in range(3) %}
  {% set total = total + i %}
{% endfor %}
{{ total }}

medium

A. The range function is not available in dbt Jinja.

B. Variables cannot be updated inside a loop.

C. The loop syntax is incorrect; missing parentheses.

D. The variable total should be declared with var.

Solution

1. Step 1: Understand Jinja in dbt limitations

   dbt uses Jinja templating, which does not support Python's range() function directly.

2. Step 2: Identify the error cause

   Using range(3) will cause an error because range is undefined in this context.

3. Final Answer:

   The range function is not available in dbt Jinja. -> Option A

4. Quick Check:

   No range() in dbt Jinja [OK]

Hint: Remember: Jinja loops use lists, not Python range() [OK]

Common Mistakes:

• Assuming Python functions work in Jinja
• Trying to update variables inside loops without workarounds
• Using wrong loop syntax

5. You want to create a dbt model that uses a variable env to switch between two schemas: dev_schema if env is 'dev', else prod_schema. Which code snippet correctly implements this control flow?

hard

A. {% set schema = 'dev_schema' if env == 'dev' else 'prod_schema' %}
SELECT * FROM {{ schema }}.my_table

B. {% if env == 'dev' %}
{% set schema = 'dev_schema' %}
{% else %}
{% set schema = 'prod_schema' %}
{% endif %}
SELECT * FROM {{ schema }}.my_table

C. {% set schema = env == 'dev' and 'dev_schema' or 'prod_schema' %}
SELECT * FROM {{ schema }}.my_table

D. {% set schema = 'prod_schema' %}
{% if env == 'dev' %}
{% set schema = 'dev_schema' %}
SELECT * FROM {{ schema }}.my_table

Solution

1. Step 1: Understand conditional variable assignment in dbt

   dbt supports control flow with {% if %} and {% else %} blocks to set variables based on conditions.

2. Step 2: Check each option for correctness

   {% if env == 'dev' %} {% set schema = 'dev_schema' %} {% else %} {% set schema = 'prod_schema' %} {% endif %} SELECT * FROM {{ schema }}.my_table uses proper if-else blocks to set schema correctly before using it in the query. {% set schema = 'dev_schema' if env == 'dev' else 'prod_schema' %} SELECT * FROM {{ schema }}.my_table uses Python-style inline if which is not supported in Jinja. {% set schema = env == 'dev' and 'dev_schema' or 'prod_schema' %} SELECT * FROM {{ schema }}.my_table uses a Python boolean expression which is not valid in Jinja. {% set schema = 'prod_schema' %} {% if env == 'dev' %} {% set schema = 'dev_schema' %} SELECT * FROM {{ schema }}.my_table sets schema first then tries to reset inside if but the query is inside the if block, causing scope issues.

3. Final Answer:

   Option B correctly uses if-else to set schema and then queries it. -> Option B

4. Quick Check:

   Use {% if %}...{% else %}...{% endif %} for control flow [OK]

Hint: Use full if-else blocks to set variables, not inline Python [OK]

Common Mistakes:

• Trying Python inline if syntax in Jinja
• Placing SQL inside if blocks incorrectly
• Not setting variable before using it