Database query optimization with select_related in Django - Step-by-Step Execution

Concept Flow - Database query optimization with select_related

Start Query

↓

Check for ForeignKey

Yes↓

Use select_related

↓

Single SQL Join Query

↓

Fetch Related Data Together

↓

Return Optimized Result

↓

End

The flow shows how select_related checks for foreign keys and fetches related data in one SQL query using joins, improving performance.

Execution Sample

Django

books = Book.objects.select_related('author').all()
for book in books:
    print(book.title, book.author.name)

This code fetches books and their authors in one query, then prints each book's title and author's name.

Execution Table

Step	Action	SQL Query	Result	Notes
1	Call select_related('author')	SELECT * FROM book JOIN author ON book.author_id = author.id	Query prepared with join	One SQL query with join ready
2	Execute query	Same as above	Database returns combined rows	Data for book and author together
3	Iterate over books	No new query	Access book.title and book.author.name	No extra queries due to select_related
4	Print output	No query	Prints book title and author name	Efficient data access
5	End iteration	No query	All data processed	No additional DB hits

💡 All books and their authors fetched in one query, no extra queries triggered during iteration

Variable Tracker

Variable	Start	After Query	After Iteration 1	After Iteration 2	Final
books	QuerySet (not evaluated)	List of Book objects with author loaded	Book object 1 with author	Book object 2 with author	All Book objects with authors

Key Moments - 2 Insights

Why does select_related reduce the number of queries?

Because select_related uses a SQL JOIN to fetch related objects in one query, as shown in execution_table step 1 and 2, avoiding separate queries per object.

What happens if we don't use select_related when accessing related fields?

Without select_related, each access to a related field triggers a new query, causing many queries during iteration, unlike the single query in execution_table step 3.

Visual Quiz - 3 Questions

Look at the execution table, what SQL query is executed at step 2?

A SELECT * FROM book JOIN author ON book.author_id = author.id

B SELECT * FROM book

C SELECT * FROM author

D No SQL query is executed

💡 Hint

Check the SQL Query column in execution_table row 2

At which step does the code avoid extra database queries when accessing author data?

A Step 1

B Step 3

C Step 4

D Step 5

💡 Hint

Look at the Result and Notes columns in execution_table row 3

If select_related was not used, how would the execution table change?

A The initial query would include a JOIN

B No queries would be executed

C More queries would appear during iteration steps

D The query would fetch unrelated data

💡 Hint

Refer to key_moments about queries triggered without select_related

Concept Snapshot

Use select_related('related_field') to fetch related objects in one SQL JOIN query.
This reduces the number of database queries during iteration.
Without it, accessing related fields triggers extra queries.
Ideal for ForeignKey and OneToOne relationships.
Improves performance by loading related data eagerly.

Full Transcript

This visual trace shows how Django's select_related optimizes database queries by using a SQL JOIN to fetch related objects in one query. Initially, select_related prepares a query joining the main and related tables. When executed, the database returns combined rows with all needed data. Iterating over the results accesses related fields without extra queries, making data retrieval efficient. Without select_related, each related field access would cause a new query, slowing down the app. This technique is best for ForeignKey or OneToOne relations to improve performance.