Why Jinja makes SQL dynamic in dbt - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to insert a Jinja variable into the SQL query.

dbt

SELECT * FROM users WHERE country = '[1]';

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

Aage_limit

Buser_id

Ccountry_var

Dorder_date

Attempts:

3 left

💡 Hint

Common Mistakes

Using a variable unrelated to the filter condition.

Forgetting to use double curly braces for Jinja variables.

The Jinja variable 'country_var' is used to dynamically insert the country value into the SQL query.

2fill in blank

medium

Complete the code to use a Jinja if-statement to add a WHERE clause only if a variable is set.

dbt

SELECT * FROM orders {% if [1] %} WHERE status = '{{ status }}' {% endif %};

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

Afilter_enabled

Bstatus

Cuser_id

Dorder_date

Attempts:

3 left

💡 Hint

Common Mistakes

Using the filter value variable instead of the control variable.

Not using the correct variable inside the if-statement.

The variable 'filter_enabled' controls whether the WHERE clause is added dynamically.

3fill in blank

hard

Fix the error in the Jinja loop that dynamically creates multiple OR conditions.

dbt

SELECT * FROM products WHERE {% for category in categories %} category = '[1]' {% if not loop.last %} OR {% endif %} {% endfor %};

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

Acategory_id

Bcategories

Ccategory.name

Dcategory

Attempts:

3 left

💡 Hint

Common Mistakes

Using the list variable instead of the loop variable.

Using an attribute that does not exist.

Inside the loop, the variable 'category' represents each item, so it should be used to insert the value.

4fill in blank

hard

Fill both blanks to create a dynamic SQL filter using Jinja with a comparison operator and a variable.

dbt

SELECT * FROM sales WHERE amount [1] [2];

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

A>

Bmin_amount

C<

Dmax_amount

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up the operator and variable positions.

Using the wrong comparison operator.

The operator '>' and variable 'min_amount' create a filter for sales greater than the minimum amount.

5fill in blank

hard

Fill all three blanks to build a dynamic CASE statement in SQL using Jinja variables.

dbt

SELECT user_id, CASE WHEN age [1] [2] THEN '[3]' ELSE 'Other' END AS age_group FROM users;

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

A<

B18

CMinor

D>=

Attempts:

3 left

💡 Hint

Common Mistakes

Using the wrong comparison operator.

Confusing the age threshold value.

Mislabeling the age group string.

The CASE statement checks if age is greater or equal (>=) to 18, then labels as 'Minor'.

Practice

1. What is the main reason Jinja is used in dbt SQL files?

easy

A. To make SQL queries dynamic by inserting variables and conditions

B. To speed up SQL query execution on the database

C. To replace SQL with a different programming language

D. To create static SQL files without any changes

Solution

1. Step 1: Understand Jinja's role in dbt

   Jinja is a templating language that allows inserting variables and logic into SQL code.

2. Step 2: Identify the benefit of dynamic SQL

   Dynamic SQL lets you reuse code with different inputs, making queries flexible and easier to maintain.

3. Final Answer:

   To make SQL queries dynamic by inserting variables and conditions -> Option A

4. Quick Check:

   Jinja = dynamic SQL [OK]

Hint: Jinja adds variables and logic to SQL for flexibility [OK]

Common Mistakes:

• Thinking Jinja speeds up SQL execution
• Confusing Jinja with a programming language
• Believing Jinja creates static SQL

2. Which of the following is the correct way to insert a variable start_date in a dbt SQL model using Jinja?

easy

A. SELECT * FROM table WHERE date >= $start_date

B. SELECT * FROM table WHERE date >= {{ start_date }}

C. SELECT * FROM table WHERE date >= :start_date

D. SELECT * FROM table WHERE date >= start_date

Solution

1. Step 1: Recognize Jinja variable syntax

   Jinja uses double curly braces {{ variable }} to insert variables into SQL.

2. Step 2: Match syntax to options

   Only SELECT * FROM table WHERE date >= {{ start_date }} uses {{ start_date }} correctly inside the SQL query.

3. Final Answer:

   SELECT * FROM table WHERE date >= {{ start_date }} -> Option B

4. Quick Check:

   Jinja variable = {{ variable }} [OK]

Hint: Use {{ variable }} to insert variables in Jinja [OK]

Common Mistakes:

• Using $ or : instead of {{ }} for variables
• Writing variable name without braces
• Confusing Jinja with SQL parameter syntax

3. Given the dbt model code:

SELECT * FROM orders WHERE order_date >= '{{ start_date }}' {% if is_active %}AND status = 'active'{% endif %}

What will be the output SQL if start_date = '2023-01-01' and is_active = False?

medium

A. SELECT * FROM orders WHERE order_date >= '2023-01-01' AND status = 'active'

B. SELECT * FROM orders WHERE order_date >= '2023-01-01' OR status = 'active'

C. SELECT * FROM orders WHERE order_date >= '2023-01-01'

D. SELECT * FROM orders WHERE order_date >= start_date

Solution

1. Step 1: Substitute the variable start_date

   The variable start_date is replaced with '2023-01-01' inside quotes.

2. Step 2: Evaluate the if condition with is_active = False

   The condition {% if is_active %} is false, so the AND clause is omitted.

3. Final Answer:

   SELECT * FROM orders WHERE order_date >= '2023-01-01' -> Option C

4. Quick Check:

   False if-block = no AND clause [OK]

Hint: If condition false means skip that SQL part [OK]

Common Mistakes:

• Including AND clause when condition is false
• Not replacing variables with values
• Confusing OR with AND in conditions

4. Identify the error in this dbt model snippet using Jinja:

SELECT * FROM users WHERE signup_date >= '{{ start_date }'

Assuming start_date is defined in the model config.

medium

A. Missing closing curly brace in variable syntax

B. Incorrect use of single quotes around variable

C. Variable name should be uppercase

D. No error, code is correct

Solution

1. Step 1: Check Jinja variable syntax

   The variable is written as '{{ start_date }' missing one closing curly brace.

2. Step 2: Understand impact of syntax error

   Missing brace causes a syntax error and Jinja will fail to render the SQL.

3. Final Answer:

   Missing closing curly brace in variable syntax -> Option A

4. Quick Check:

   Variable syntax needs {{ and }} [OK]

Hint: Count curly braces: must be two on each side [OK]

Common Mistakes:

• Forgetting one curly brace
• Thinking quotes cause error
• Assuming variable case matters

5. You want to create a dbt model that filters sales data by region only if a variable filter_region is set. Which Jinja code snippet correctly implements this dynamic filter?

hard

A. WHERE region = '{{ filter_region }}' OR TRUE

B. {% if filter_region %}AND region = filter_region{% endif %}

C. WHERE region = filter_region

D. {% if filter_region %}WHERE region = '{{ filter_region }}'{% endif %}

Solution

1. Step 1: Use if condition to add filter only when variable exists

   The filter should appear only if filter_region has a value, so use {% if filter_region %}.

2. Step 2: Insert variable correctly inside quotes

   Use '{{ filter_region }}' to insert the variable value as a string in SQL.

3. Step 3: Ensure correct SQL syntax

   {% if filter_region %}WHERE region = '{{ filter_region }}'{% endif %} adds a WHERE clause only when needed, avoiding syntax errors.

4. Final Answer:

   {% if filter_region %}WHERE region = '{{ filter_region }}'{% endif %} -> Option D

5. Quick Check:

   Conditional WHERE with {{ variable }} [OK]

Hint: Use if-block to add WHERE only if variable set [OK]

Common Mistakes:

• Adding filter unconditionally causing errors
• Not quoting variable values in SQL
• Using AND without preceding WHERE