For loops for dynamic SQL in dbt - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to start a for loop over the list 'tables'.

dbt

{% for [1] in tables %}
  SELECT * FROM [1]
{% endfor %}

Drag options to blanks, or click blank then click option'

Atable

Btables

Ci

Ditem

Attempts:

3 left

💡 Hint

Common Mistakes

Using the list name 'tables' instead of a single item variable.

Using an index variable like 'i' which is not typical in dbt loops.

In dbt Jinja, the variable name in the for loop should be a single item, like 'table', not the list itself.

2fill in blank

medium

Complete the code to output the table name inside the loop.

dbt

{% for table in tables %}
  SELECT * FROM {{ [1] }}
{% endfor %}

Drag options to blanks, or click blank then click option'

Atables

Btable

Cloop.index

Ditem

Attempts:

3 left

💡 Hint

Common Mistakes

Using the list name 'tables' inside the loop instead of the loop variable.

Using 'loop.index' which is a number, not a table name.

Inside the loop, use the loop variable 'table' to refer to the current table name.

3fill in blank

hard

Fix the error in the loop syntax to correctly iterate over 'columns'.

dbt

{% for col [1] columns %}
  {{ col }}
{% endfor %}

Drag options to blanks, or click blank then click option'

Ain

Bon

Cof

Dat

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'of' or 'on' instead of 'in' causes syntax errors.

Leaving out the keyword entirely.

The correct syntax for a for loop in Jinja is 'for variable in list'.

4fill in blank

hard

Fill all three blanks to create a dictionary comprehension that maps columns to their types if type is 'string'.

dbt

{% set col_types = { [1]: [2] for [3] in columns if columns[[3]] == 'string' } %}

Drag options to blanks, or click blank then click option'

Acol

Bcolumns[col]

Attempts:

3 left

💡 Hint

Common Mistakes

Using the list name 'columns' as key or value directly.

Mixing variable names inconsistently.

The key is the column name 'col', and the value is its type 'columns[col]'.

5fill in blank

hard

Fill all three blanks to create a loop that builds a SQL SELECT statement with dynamic columns and tables.

dbt

{% set select_cols = ', '.join([[1] for [2] in columns]) %}
SELECT {{select_cols}} FROM [3]

Drag options to blanks, or click blank then click option'

Acol

Ctable

Dcolumns

Attempts:

3 left

💡 Hint

Common Mistakes

Using different variable names in the list comprehension and loop.

Using the list name 'columns' instead of the variable.

Using 'columns' as the table name.

We use 'col' as the variable in the list comprehension and loop, and 'table' as the table name.

Practice

1. What is the main purpose of using {% for %} loops in dbt SQL models?

easy

A. To create permanent tables in the database

B. To stop SQL queries from running

C. To write Python code inside SQL models

D. To repeat SQL code patterns dynamically and reduce manual repetition

Solution

1. Step 1: Understand the role of {% for %} in dbt

   The {% for %} loop is used to repeat code blocks dynamically in dbt SQL models.

2. Step 2: Identify the benefit of repeating code

   Repeating code patterns saves time and reduces errors by avoiding manual copy-pasting.

3. Final Answer:

   To repeat SQL code patterns dynamically and reduce manual repetition -> Option D

4. Quick Check:

   For loops = dynamic repetition [OK]

Hint: For loops repeat code blocks automatically in dbt [OK]

Common Mistakes:

• Thinking for loops create tables
• Confusing dbt loops with Python loops
• Believing loops stop queries

2. Which of the following is the correct syntax to start a for loop in a dbt SQL model?

easy

A. {% loop item in list %}

B. {{ for item in list }}

C. {% for item in list %}

D. <% for item in list %>

Solution

1. Step 1: Recall dbt Jinja syntax for loops

   dbt uses Jinja templating where loops start with {% for variable in sequence %}.

2. Step 2: Compare options to correct syntax

   Only {% for item in list %} matches the correct Jinja for loop syntax.

3. Final Answer:

   {% for item in list %} -> Option C

4. Quick Check:

   dbt for loop syntax = {% for %} [OK]

Hint: dbt loops start with {% for variable in sequence %} [OK]

Common Mistakes:

• Using {{ }} instead of {% %} for loops
• Using wrong keywords like 'loop'
• Using angle brackets instead of curly braces

3. Given the following dbt code snippet, what will be the output SQL?

{% for col in ['id', 'name', 'age'] %}SELECT {{ col }} FROM users{% if not loop.last %} UNION ALL {% endif %}{% endfor %}

medium

A. SELECT id FROM users UNION ALL SELECT name FROM users UNION ALL SELECT age FROM users

B. SELECT id, name, age FROM users

C. SELECT id FROM users SELECT name FROM users SELECT age FROM users

D. SyntaxError due to missing commas

Solution

1. Step 1: Understand the loop iteration

   The loop runs over ['id', 'name', 'age'], producing three SELECT statements.

2. Step 2: Check the UNION ALL insertion

   Between each SELECT except the last, 'UNION ALL' is added to combine results.

3. Final Answer:

   SELECT id FROM users UNION ALL SELECT name FROM users UNION ALL SELECT age FROM users -> Option A

4. Quick Check:

   Loop + UNION ALL = combined selects [OK]

Hint: Look for loop.last to add UNION ALL except last [OK]

Common Mistakes:

• Ignoring the UNION ALL between selects
• Assuming all columns selected in one query
• Thinking commas separate selects

4. Identify the error in this dbt for loop snippet:

{% for col in columns %}SELECT {{ col }} FROM users{% endfor %}

Assuming columns = ['id', 'name'].

medium

A. Wrong loop syntax with {{ }} instead of {% %}

B. Missing UNION ALL or separator between SELECT statements

C. Incorrect variable name inside the loop

D. Loop variable should be capitalized

Solution

1. Step 1: Analyze the loop output

   The loop outputs two SELECT statements back to back without any separator.

2. Step 2: Identify missing SQL syntax

   Without UNION ALL or a separator, the SQL is invalid and will cause errors.

3. Final Answer:

   Missing UNION ALL or separator between SELECT statements -> Option B

4. Quick Check:

   Multiple SELECTs need UNION ALL [OK]

Hint: Add UNION ALL between selects in loops [OK]

Common Mistakes:

• Forgetting to add UNION ALL
• Using wrong loop syntax
• Misnaming variables inside loop

5. You want to create a dynamic SQL query in dbt that selects multiple columns from a table, but only if the column name is not empty or None. Which for loop code snippet correctly achieves this?

hard

A. {% for col in columns if col %}SELECT {{ col }} FROM users{% if not loop.last %} UNION ALL {% endif %}{% endfor %}

B. {% for col in columns %}SELECT {{ col }} FROM users{% if col != '' or col != None %} UNION ALL {% endif %}{% endfor %}

C. {% for col in columns %}{% if col %}SELECT {{ col }} FROM users UNION ALL {% endif %}{% endfor %}

D. {% for col in columns %}SELECT {{ col }} FROM users UNION ALL {% endfor %}

Solution

1. Step 1: Filter columns inside the for loop

   {% for col in columns if col %}SELECT {{ col }} FROM users{% if not loop.last %} UNION ALL {% endif %}{% endfor %} uses for col in columns if col to skip empty or None values correctly.

2. Step 2: Add UNION ALL only between valid selects

   {% for col in columns if col %}SELECT {{ col }} FROM users{% if not loop.last %} UNION ALL {% endif %}{% endfor %} adds UNION ALL only if not the last valid column, avoiding trailing UNION ALL.

3. Final Answer:

   {% for col in columns if col %}SELECT {{ col }} FROM users{% if not loop.last %} UNION ALL {% endif %}{% endfor %} -> Option A

4. Quick Check:

   Filter in loop + conditional UNION ALL = correct [OK]

Hint: Use 'if col' in loop to skip empty values [OK]

Common Mistakes:

• Using incorrect if condition syntax
• Adding UNION ALL after last select
• Not filtering out empty or None columns