F expressions for field comparisons in Django - Step-by-Step Execution

Concept Flow - F expressions for field comparisons

Start Query

↓

Use F expression

↓

Compare model fields

↓

Generate SQL with field references

↓

Execute query

↓

Return filtered results

This flow shows how Django uses F expressions to compare fields within the same model in a query.

Execution Sample

Django

from django.db.models import F

# Filter products where price > cost
Product.objects.filter(price__gt=F('cost'))

This code filters Product records where the price field is greater than the cost field using an F expression.

Execution Table

Step	Action	F Expression Evaluation	SQL Generated	Query Result
1	Start filter query	N/A	SELECT * FROM product	No results yet
2	Apply filter price__gt=F('cost')	Compare price and cost fields	SELECT * FROM product WHERE price > cost	Query prepared
3	Execute query	Database compares price and cost per row	N/A	Returns products with price > cost
4	End	N/A	N/A	Filtered queryset returned

💡 Query completes after filtering all rows where price is greater than cost

Variable Tracker

Variable	Start	After Step 2	After Step 3	Final
queryset	All products	Filtered by price > cost	Executed query	Filtered products returned

Key Moments - 2 Insights

Why do we use F('cost') instead of just 'cost' in the filter?

Using F('cost') tells Django to compare the database field 'cost' directly, not a fixed value. See execution_table step 2 where the SQL uses price > cost.

Does the comparison happen in Python or in the database?

The comparison happens in the database as shown in execution_table step 3, where the SQL query compares fields for each row.

Visual Quiz - 3 Questions

Look at the execution_table, what SQL is generated at step 2?

A SELECT * FROM product WHERE price > 100

B SELECT * FROM product WHERE price > cost

C SELECT * FROM product WHERE price > 'cost'

D SELECT * FROM product

💡 Hint

Check the 'SQL Generated' column at step 2 in the execution_table

At which step does the database compare the fields price and cost?

A Step 3

B Step 1

C Step 2

D Step 4

💡 Hint

Look at the 'Action' and 'Query Result' columns in execution_table step 3

If we replaced F('cost') with a fixed value 50, how would the SQL change at step 2?

A SELECT * FROM product WHERE price > 'cost'

B SELECT * FROM product WHERE price > cost

C SELECT * FROM product WHERE price > 50

D SELECT * FROM product

💡 Hint

Think about how fixed values appear in SQL compared to field references in execution_table step 2

Concept Snapshot

F expressions let you compare model fields directly in queries.
Use F('fieldname') inside filters to refer to another field.
Django generates SQL comparing columns, not fixed values.
This runs in the database for efficiency.
Example: filter(price__gt=F('cost')) finds rows where price > cost.

Full Transcript

This visual trace shows how Django's F expressions work for comparing fields in a query. First, the query starts with all products. Then, using filter(price__gt=F('cost')), Django prepares SQL that compares the price and cost columns directly. The database executes this SQL, returning only products where price is greater than cost. The key is that F('cost') tells Django to use the database field, not a fixed value. This makes the comparison efficient and dynamic. The variable 'queryset' changes from all products to the filtered set after the query runs. Understanding this flow helps beginners see how Django builds and runs queries with field comparisons.