Prefetch_related for reverse relations in Django - Step-by-Step Execution

Concept Flow - Prefetch_related for reverse relations

Query main model

↓

Identify reverse relation

↓

Create separate query for related objects

↓

Fetch related objects in bulk

↓

Link related objects to main model instances

↓

Return combined result with prefetched data

Django fetches main model data first, then separately fetches related objects via reverse relation, and links them to avoid extra queries later.

Execution Sample

Django

authors = Author.objects.prefetch_related('book_set').all()
for author in authors:
    print(author.name, [book.title for book in author.book_set.all()])

Fetch authors and their related books efficiently using prefetch_related on reverse relation 'book_set'.

Execution Table

Step	Action	Query Executed	Result	Notes
1	Fetch all authors	SELECT * FROM author;	List of authors	Main query to get authors
2	Identify reverse relation 'book_set'	N/A	Prepare to fetch books	Recognize reverse FK from Book to Author
3	Fetch books for all authors in one query	SELECT * FROM book WHERE author_id IN (author_ids);	List of books	Bulk fetch books related to authors
4	Link books to each author instance	N/A	author.book_set populated	Attach books to authors in memory
5	Iterate authors and print books	N/A	Print author names and their book titles	No extra queries during iteration
6	End	N/A	All data fetched efficiently	Prefetch_related avoids N+1 query problem

💡 All authors and their related books fetched with only two queries, avoiding multiple database hits.

Variable Tracker

Variable	Start	After Step 1	After Step 3	After Step 4	Final
authors	empty	List of Author objects	Same list, books not linked yet	Authors with book_set linked	Authors with book_set linked
books	empty	empty	List of Book objects related to authors	Books linked to authors	Books linked to authors

Key Moments - 3 Insights

Why does prefetch_related run two queries instead of one?

Prefetch_related runs one query for the main model and a separate query for the related objects to efficiently fetch reverse relations in bulk, as shown in execution_table steps 1 and 3.

How does Django link the related objects to the main model after fetching?

After fetching related objects in step 3, Django attaches them to each main model instance in memory (step 4), so accessing reverse relations does not trigger new queries.

What problem does prefetch_related solve when accessing reverse relations?

It prevents the N+1 query problem where accessing each related set would cause a separate query, by fetching all related objects in one query and linking them upfront (see steps 3 and 4).

Visual Quiz - 3 Questions

Look at the execution_table, at which step are the related books fetched from the database?

A Step 1

B Step 3

C Step 4

D Step 5

💡 Hint

Check the 'Query Executed' column for the step fetching books.

According to variable_tracker, when do authors get their book_set linked?

A After Step 4

B After Step 3

C After Step 1

D At Start

💡 Hint

Look at the 'authors' row and see when book_set is populated.

If prefetch_related was not used, what would happen during iteration in Step 5?

A No queries would run

B One query for all books would run

C A query per author to fetch books would run

D An error would occur

💡 Hint

Recall the N+1 query problem explained in key_moments.

Concept Snapshot

prefetch_related('reverse_relation') fetches related objects in a separate query.
It avoids multiple queries when accessing reverse foreign key sets.
Django runs two queries: one for main model, one for related objects.
Related objects are linked in memory for fast access.
Use it to improve performance when accessing reverse relations.

Full Transcript

This visual execution trace shows how Django's prefetch_related works for reverse relations. First, Django queries the main model (authors). Then it identifies the reverse relation (book_set) and fetches all related books in one query. After fetching, Django links these books to their respective authors in memory. This process avoids running a separate query for each author when accessing their books, solving the N+1 query problem. The variable tracker shows authors and books before and after linking. Key moments clarify why two queries run and how linking happens. The quiz tests understanding of when queries run and how data links. Overall, prefetch_related improves efficiency by batching related data fetching for reverse relations.