Chaining querysets in Django - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What is the output count of this chained queryset?

Given two querysets qs1 and qs2 from the same Django model, what will be the count of combined_qs = qs1 | qs2 if qs1 has 3 items and qs2 has 4 items with 2 overlapping records?

Django

qs1 = Model.objects.filter(field__startswith='A')  # 3 items
qs2 = Model.objects.filter(field__endswith='Z')      # 4 items
combined_qs = qs1 | qs2
print(combined_qs.count())

A 5

B 7

C 6

D 4

💡 Hint

Remember that chaining with | combines unique records from both querysets.

The | operator combines two querysets and removes duplicates. Since 2 records overlap, total unique records are 3 + 4 - 2 = 5.

📝 Syntax

intermediate

Which option correctly chains querysets to filter users?

You want to get all users who are either staff or have a verified email. Which queryset chaining syntax is correct?

Django

staff_qs = User.objects.filter(is_staff=True)
verified_qs = User.objects.filter(email_verified=True)
combined_qs = ???

A combined_qs = staff_qs | verified_qs

B combined_qs = staff_qs + verified_qs

C combined_qs = staff_qs & verified_qs

D combined_qs = staff_qs.filter(verified_qs)

💡 Hint

Use the operator that combines two querysets including all unique records from both.

The | operator combines two querysets with an OR condition, including unique records from both. The & operator is for intersection (AND).

🔧 Debug

advanced

Why does this chained queryset raise an error?

Consider these querysets from different models. Why does chaining them with | cause an error?

Django

qs1 = Author.objects.filter(active=True)
qs2 = Book.objects.filter(published=True)
combined_qs = qs1 | qs2

A You must convert querysets to lists before chaining

B You cannot chain querysets with filter conditions

C The | operator only works with lists, not querysets

D Querysets must be from the same model to be chained with |

💡 Hint

Check the model type of each queryset before chaining.

The | operator requires both querysets to be from the same model. Here, Author and Book are different models, so chaining raises a TypeError.

❓ state_output

advanced

What is the output of this chained queryset with exclusion?

Given qs1 with 5 items and qs2 with 3 items (all in qs1), what is the count of result_qs = qs1.exclude(pk__in=qs2)?

Django

qs1 = Model.objects.filter(active=True)  # 5 items
qs2 = Model.objects.filter(active=True, status='inactive')  # 3 items, all in qs1
result_qs = qs1.exclude(pk__in=qs2)
print(result_qs.count())

A 0

B 5

C 2

D 3

💡 Hint

Excluding items in qs2 removes those 3 from qs1.

The exclude removes the 3 items from qs1 that are in qs2, leaving 2 items.

🧠 Conceptual

expert

Why is chaining querysets with | preferred over concatenating lists?

Which reason best explains why chaining querysets with | is better than converting querysets to lists and concatenating them?

A List concatenation preserves database query optimizations, chaining does not

B Chaining with | keeps the query lazy and efficient, while list concatenation loads all data immediately

C Chaining querysets with | only works on small datasets, lists work on large datasets

D List concatenation automatically removes duplicates, but chaining does not

💡 Hint

Think about when the database query runs in each case.

Using | chains querysets lazily, so the database query runs only when needed, improving performance. Converting to lists fetches all data immediately, which can be slow and memory-heavy.