Relationship query patterns in Django - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a ForeignKey in Django models?

A ForeignKey is a field used to create a many-to-one relationship between two models. It links one model to another by storing the related model's primary key.

beginner

How do you access related objects in a one-to-many relationship in Django?

You use the related manager on the 'one' side to access all related 'many' objects. For example, if a Book has a ForeignKey to Author, you can get all books of an author with author.book_set.all().

intermediate

What does select_related() do in Django queries?

select_related() performs a SQL join and fetches related objects in the same query, reducing database hits for foreign key and one-to-one relationships.

intermediate

When should you use prefetch_related() in Django?

Use prefetch_related() to fetch many-to-many or reverse foreign key relationships efficiently. It runs separate queries and joins in Python to reduce database hits.

beginner

How do you filter objects based on related model fields in Django?

You use double underscores to span relationships in filter() calls. For example, Book.objects.filter(author__name='Alice') filters books where the related author's name is Alice.

Which Django method fetches related objects in the same database query for ForeignKey relationships?

A select_related()

B prefetch_related()

C filter()

D annotate()

select_related() uses SQL joins to fetch related objects in one query, ideal for ForeignKey and OneToOne fields.

How do you access all related objects from the 'one' side in a one-to-many relationship?

A Use related_manager.all() like author.book_set.all()

B Use select_related()

C Use filter() on the related model only

D Use prefetch_related() on the 'one' side

The related manager (like book_set) lets you get all related objects from the 'one' side.

Which method is best for optimizing queries involving many-to-many relationships?

A select_related()

B prefetch_related()

C filter()

D exclude()

prefetch_related() runs separate queries and joins in Python, ideal for many-to-many relationships.

How do you filter a queryset by a field in a related model?

A Use select_related() only

B Use dot notation, e.g., filter(author.name='Alice')

C Use join() method

D Use double underscores, e.g., filter(author__name='Alice')

Django uses double underscores to traverse relationships in filters.

What is the default related manager name for a ForeignKey from model Book to Author?

A author_set

B books

C book_set

D author_books

The default related manager on the 'one' side is modelname_set, so author.book_set accesses related books.

Explain how to efficiently query related objects in Django using select_related() and prefetch_related().

Think about the type of relationship and how data is fetched.

Describe how to filter a Django queryset based on fields in a related model.

Focus on the syntax for accessing related fields in filters.

Practice

1. In Django, how do you filter a queryset to get all Book objects where the related Author model's name is 'Alice'?

easy

A. Book.objects.filter(author.name='Alice')

B. Book.objects.filter(name__author='Alice')

C. Book.objects.filter('author.name'='Alice')

D. Book.objects.filter(author__name='Alice')

Solution

1. Step 1: Understand Django's double underscore syntax for related fields

   In Django ORM, to filter by a related model's field, use double underscores between the related model name and the field name.

2. Step 2: Apply the correct filter syntax

   Here, author__name='Alice' correctly filters books whose author's name is 'Alice'.

3. Final Answer:

   Book.objects.filter(author__name='Alice') -> Option D

4. Quick Check:

   Related field filter uses __ = A [OK]

Hint: Use double underscores to filter related model fields [OK]

Common Mistakes:

• Using dot notation instead of double underscores
• Reversing the field and model names
• Passing strings incorrectly in filter

2. Which of the following is the correct syntax to use select_related to optimize a query fetching Book objects with their related Author data?

easy

A. Book.objects.select_related(['author']).all()

B. Book.objects.select_related(author).all()

C. Book.objects.select_related('author').all()

D. Book.objects.select_related('author__name').all()

Solution

1. Step 1: Recall the correct argument type for select_related

   select_related accepts one or more string arguments naming related fields to follow.

2. Step 2: Check the syntax for passing related field names

   Passing a string like 'author' is correct. Passing a variable without quotes or a list is incorrect.

3. Final Answer:

   Book.objects.select_related('author').all() -> Option C

4. Quick Check:

   select_related takes string field names [OK]

Hint: Pass related field names as strings to select_related [OK]

Common Mistakes:

• Passing variables without quotes
• Using lists instead of strings
• Including field names beyond direct relations

3. Given these models:

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

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

What will this query return?

books = Book.objects.filter(author__name__startswith='J')

medium

A. All authors whose name starts with 'J'

B. All books whose author's name starts with 'J'

C. All books with title starting with 'J'

D. Syntax error due to incorrect filter

Solution

1. Step 1: Understand the filter condition

   The filter uses author__name__startswith='J', which means it looks at the related author's name starting with 'J'.

2. Step 2: Determine the queryset result

   The queryset returns Book objects whose related Author name starts with 'J'.

3. Final Answer:

   All books whose author's name starts with 'J' -> Option B

4. Quick Check:

   Filter on related field with startswith = A [OK]

Hint: Filter related fields with double underscores and lookups [OK]

Common Mistakes:

• Confusing filtering on book title instead of author name
• Thinking the query returns authors instead of books
• Misusing lookup syntax causing errors

4. Identify the error in this Django query:

Book.objects.prefetch_related('author__books').all()

Assuming Author has a reverse relation books to Book.

medium

A. No error, the query is correct

B. The lookup 'author__books' is invalid for prefetch_related

C. prefetch_related requires a list, not a string

D. prefetch_related cannot follow reverse relations

Solution

1. Step 1: Understand prefetch_related capabilities

   prefetch_related supports double-underscore chained lookups across forward (FK) and reverse relations.

2. Step 2: Validate the lookup 'author__books'

   From Book, 'author' follows the FK to Author, then 'books' follows the reverse relation to Book objects. This is valid and prefetches all books per author.

3. Final Answer:

   No error, the query is correct -> Option A

4. Quick Check:

   prefetch_related supports FK + reverse chains [OK]

Hint: prefetch_related supports chained lookups including reverse relations [OK]

Common Mistakes:

• Thinking prefetch_related cannot chain to reverse relations
• Passing a list instead of a string
• Assuming prefetch_related cannot follow reverse relations

5. You want to efficiently fetch all Book objects along with their Author and the Publisher related to the author. The models are:

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

class Author(models.Model):
    name = models.CharField(max_length=100)
    publisher = models.ForeignKey(Publisher, on_delete=models.CASCADE)

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

Which query optimizes database hits best?

hard

A. Book.objects.select_related('author', 'author__publisher').all()

B. Book.objects.prefetch_related('author', 'author__publisher').all()

C. Book.objects.select_related('author').prefetch_related('author__publisher').all()

D. Book.objects.all()

Solution

1. Step 1: Understand select_related vs prefetch_related

   select_related follows foreign keys with SQL JOINs, efficient for single-valued relations. prefetch_related is for many-to-many or reverse relations.

2. Step 2: Analyze the relations

   Both author and author__publisher are foreign keys (single-valued), so select_related is best to reduce queries.

3. Final Answer:

   Book.objects.select_related('author', 'author__publisher').all() -> Option A

4. Quick Check:

   Use select_related for foreign keys chains [OK]

Hint: Use select_related for foreign key chains to reduce queries [OK]

Common Mistakes:

• Using prefetch_related for foreign keys
• Not chaining related fields in select_related
• Fetching all without optimization