Prefetch_related for reverse relations in Django - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What does prefetch_related do with reverse relations?

Consider two Django models: Author and Book, where Book has a foreign key to Author. If you use Author.objects.prefetch_related('book_set'), what is the main effect?

A It does not affect the query and fetches authors without related books.

B It joins the author and book tables in one query using SQL JOIN.

C It fetches only the first book for each author to optimize performance.

D It fetches all related books for each author in a single additional query, reducing database hits.

💡 Hint

Think about how Django avoids querying the database multiple times for related objects.

prefetch_related fetches related objects in a separate query and joins them in Python, which is efficient for reverse relations like book_set.

❓ state_output

intermediate

How many queries are executed with prefetch_related on reverse relation?

Given the models Author and Book (with Book.author as ForeignKey), what is the number of database queries executed by this code?

authors = Author.objects.prefetch_related('book_set').all()
for author in authors:
    print(len(author.book_set.all()))

A No queries: data is fetched lazily when printing.

B 1 query: a single JOIN query fetching authors and books.

C 2 queries: one for authors and one for all related books.

D N+1 queries: one for authors and one per author for books.

💡 Hint

Remember how prefetch_related works internally with separate queries.

prefetch_related runs one query for the main model and one for the related model, then combines results in Python, so total 2 queries.

🔧 Debug

advanced

Why does prefetch_related('books') raise an error on reverse relation?

Given models Author and Book where Book.author is a ForeignKey, what is wrong with this query?

Author.objects.prefetch_related('books').all()

Assuming no related_name is set on Book.author.

A prefetch_related cannot be used on reverse relations without related_name.

B The related name 'books' does not exist; the default reverse relation is 'book_set'.

C The query will run but return empty related objects.

D The query causes a syntax error due to missing parentheses.

💡 Hint

Check the default reverse relation name Django uses when no related_name is set.

Without a related_name, Django uses modelname_set as the reverse relation name, so books is invalid.

📝 Syntax

advanced

Which prefetch_related syntax correctly fetches nested reverse relations?

Given models Author, Book, and Chapter where Book has ForeignKey to Author and Chapter has ForeignKey to Book, which syntax correctly prefetches all books and their chapters for authors?

A Author.objects.prefetch_related('book_set__chapter_set').all()

B Author.objects.prefetch_related('book_set.chapter_set').all()

C Author.objects.prefetch_related(['book_set', 'chapter_set']).all()

D Author.objects.prefetch_related('book_set').prefetch_related('chapter_set').all()

💡 Hint

Think about how to specify nested relations in prefetch_related.

Use double underscores to chain reverse relations in prefetch_related. Option A is correct syntax.

🧠 Conceptual

expert

Why use Prefetch object with custom queryset on reverse relation?

When prefetching a reverse relation in Django, why might you use Prefetch with a custom queryset instead of a simple string?

A To filter or order the related objects before they are attached to the main objects.

B To force Django to use SQL JOIN instead of separate queries.

C To disable caching of related objects for memory optimization.

D To automatically update related objects in the database.

💡 Hint

Consider why you might want to control which related objects are fetched.

The Prefetch object lets you specify a custom queryset to filter, order, or annotate related objects before they are attached, improving query control.

Practice

1. What is the main purpose of using prefetch_related with reverse relations in Django?

easy

A. To update related objects in bulk

B. To fetch related objects in a single query and reduce database hits

C. To delete related objects automatically

D. To create new related objects during query

Solution

1. Step 1: Understand what prefetch_related does

   prefetch_related fetches related objects in a separate query but combines results in Python to reduce database hits.

2. Step 2: Apply this to reverse relations

   Using prefetch_related on reverse relations loads all related objects efficiently, avoiding queries inside loops.

3. Final Answer:

   To fetch related objects in a single query and reduce database hits -> Option B

4. Quick Check:

   prefetch_related reduces queries [OK]

Hint: Remember: prefetch_related loads reverse relations in one go [OK]

Common Mistakes:

• Thinking prefetch_related deletes or updates data
• Confusing prefetch_related with select_related
• Assuming it creates new objects automatically

2. Which of the following is the correct syntax to prefetch a reverse relation named comments on a Post model?

easy

A. Post.objects.prefetch_related(comments)

B. Post.objects.select_related('comments')

C. Post.objects.prefetch('comments')

D. Post.objects.prefetch_related('comments')

Solution

1. Step 1: Recall the correct method name

   The correct method to prefetch related objects is prefetch_related, not prefetch or select_related for reverse relations.

2. Step 2: Check the argument format

   The related name must be a string inside quotes, so 'comments' is correct, not a variable without quotes.

3. Final Answer:

   Post.objects.prefetch_related('comments') -> Option D

4. Quick Check:

   Correct method and string argument [OK]

Hint: Use prefetch_related('relation_name') with quotes [OK]

Common Mistakes:

• Using select_related for reverse relations
• Omitting quotes around relation name
• Using a non-existent method like prefetch()

3. Given these models:

class Author(models.Model):
    name = models.CharField(max_length=100)

class Book(models.Model):
    author = models.ForeignKey(Author, related_name='books', on_delete=models.CASCADE)
    title = models.CharField(max_length=100)

What will this code print?

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

medium

A. Prints author names but book lists are empty

B. Raises an error because 'books' is not a valid relation

C. Prints each author name with a list of their book titles without extra queries

D. Prints author names but causes a query for each author inside the loop

Solution

1. Step 1: Understand the model relation

   Each Author has many Book objects accessible via the reverse relation books.

2. Step 2: Analyze the prefetch_related effect

   Using prefetch_related('books') loads all books for all authors in one extra query, so no queries happen inside the loop.

3. Final Answer:

   Prints each author name with a list of their book titles without extra queries -> Option C

4. Quick Check:

   prefetch_related loads reverse relations efficiently [OK]

Hint: prefetch_related loads reverse sets before looping [OK]

Common Mistakes:

• Thinking prefetch_related causes errors if relation exists
• Assuming empty lists because of missing select_related
• Believing queries run inside the loop despite prefetch

4. What is wrong with this code snippet?

posts = Post.objects.prefetch_related('comment_set')
for post in posts:
    print(post.title, [c.text for c in post.comment_set.all()])

Assuming Comment model has a ForeignKey to Post without a related_name set.

medium

A. Using 'comment_set' is correct; no error here

B. Should use 'comments' instead of 'comment_set' in prefetch_related

C. Must use select_related instead of prefetch_related for reverse relations

D. The code will raise an AttributeError because 'comment_set' is invalid

Solution

1. Step 1: Understand default reverse relation naming

   If no related_name is set on a ForeignKey, Django uses modelname_set as the reverse relation name, here comment_set.

2. Step 2: Check usage in prefetch_related and loop

   Using prefetch_related('comment_set') and accessing post.comment_set.all() is correct and will work without error.

3. Final Answer:

   Using 'comment_set' is correct; no error here -> Option A

4. Quick Check:

   Default reverse name = modelname_set [OK]

Hint: Default reverse name is modelname_set if no related_name [OK]

Common Mistakes:

• Assuming related_name is always 'comments'
• Using select_related for reverse relations
• Expecting an error when using default reverse name

5. You want to efficiently load all Author objects with their Book objects, but only books published after 2020. How do you use prefetch_related for this filtered reverse relation?

authors = Author.objects.prefetch_related( ... )

hard

A. Use Prefetch with a filtered queryset: Prefetch('books', queryset=Book.objects.filter(pub_year__gt=2020))

B. Use prefetch_related('books').filter(pub_year__gt=2020)

C. Use select_related('books').filter(pub_year__gt=2020)

D. Use prefetch_related('books__filter(pub_year__gt=2020)')

Solution

1. Step 1: Understand filtering reverse relations with prefetch_related

   To filter related objects in prefetch_related, use the Prefetch object with a filtered queryset.

2. Step 2: Apply Prefetch with filtered queryset

   Use Prefetch('books', queryset=Book.objects.filter(pub_year__gt=2020)) inside prefetch_related() to load only books after 2020.

3. Final Answer:

   Use Prefetch with a filtered queryset: Prefetch('books', queryset=Book.objects.filter(pub_year__gt=2020)) -> Option A

4. Quick Check:

   Filtered prefetch needs Prefetch object [OK]

Hint: Use Prefetch with filtered queryset inside prefetch_related [OK]

Common Mistakes:

• Trying to filter directly inside prefetch_related string
• Using select_related for many-to-one reverse relations
• Filtering the main queryset instead of related queryset