Why querysets are lazy and powerful in Django - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a queryset that fetches all objects from the model.

Django

all_items = Model.objects.[1]()

Drag options to blanks, or click blank then click option'

Aall

Bfilter

Cget

Dcreate

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'get' instead of 'all' which returns a single object, not a queryset.

Using 'create' which inserts a new object instead of fetching.

The all() method returns a queryset of all objects in the model. It does not hit the database immediately, making it lazy.

2fill in blank

medium

Complete the code to filter objects where 'status' is 'active'.

Django

active_items = Model.objects.[1](status='active')

Drag options to blanks, or click blank then click option'

Aall

Bget

Cexclude

Dfilter

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'get' which returns a single object and raises error if multiple found.

Using 'exclude' which returns objects not matching the condition.

The filter() method returns a lazy queryset with objects matching the condition. It does not query the database until needed.

3fill in blank

hard

Fix the error in the code to get the first object or None without hitting the database multiple times.

Django

first_item = Model.objects.[1]().first()

Drag options to blanks, or click blank then click option'

Aget

Bfilter

Call

Dexclude

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'get' which raises exceptions if multiple or no objects found.

Using 'filter' without calling first() to get a single object.

The all() method returns a queryset, and calling first() on it fetches the first object or None efficiently. Using get() would raise errors if multiple objects exist.

4fill in blank

hard

Fill both blanks to create a queryset that orders items by 'created' date descending and limits to 5 results.

Django

recent_items = Model.objects.[1]('-created')[:[2]]

Drag options to blanks, or click blank then click option'

Aorder_by

Bfilter

C5

D10

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'filter' instead of 'order_by' for sorting.

Using a wrong number for slicing.

The order_by('-created') sorts the queryset by 'created' date descending. Using slicing [:5] limits the results to 5. Both together create a lazy, efficient query.

5fill in blank

hard

Fill all three blanks to create a dictionary comprehension that maps usernames to emails for users active and joined after 2020.

Django

user_dict = {user.[1]: user.[2] for user in User.objects.[3](is_active=True, joined__year__gt=2020)}

Drag options to blanks, or click blank then click option'

Ausername

Bemail

Cfilter

Dall

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'all' instead of 'filter' which does not apply conditions.

Swapping username and email in the dictionary keys and values.

This comprehension creates a dictionary with usernames as keys and emails as values. The queryset uses filter() to select active users who joined after 2020. This is lazy and efficient.

Practice

1. Why are Django querysets considered lazy?

easy

A. They only work with small datasets

B. They immediately fetch all data when created

C. They store data permanently in memory

D. They delay database access until the data is actually needed

Solution

1. Step 1: Understand queryset creation

   When you create a queryset, Django does not immediately fetch data from the database.

2. Step 2: Recognize when data is fetched

   Data is only retrieved when you actually use the queryset, like iterating or converting it to a list.

3. Final Answer:

   They delay database access until the data is actually needed -> Option D

4. Quick Check:

   Querysets fetch data lazily = A [OK]

Hint: Querysets wait to fetch data until you use them [OK]

Common Mistakes:

• Thinking querysets fetch data immediately
• Confusing lazy evaluation with caching
• Assuming querysets store all data in memory

2. Which of the following is the correct way to add a filter to a Django queryset without hitting the database immediately?

easy

A. MyModel.objects.create(name='Alice')

B. MyModel.objects.filter(name='Alice')

C. MyModel.objects.get(name='Alice')

D. MyModel.objects.all()

Solution

1. Step 1: Identify queryset methods

   The filter() method returns a queryset and does not hit the database immediately.

2. Step 2: Compare with other methods

   get() fetches a single object immediately, create() inserts data, and all() returns all objects but still lazy.

3. Final Answer:

   MyModel.objects.filter(name='Alice') -> Option B

4. Quick Check:

   filter() adds conditions lazily = D [OK]

Hint: filter() builds query lazily, get() fetches immediately [OK]

Common Mistakes:

• Using get() expecting lazy behavior
• Confusing create() with filter()
• Thinking all() fetches data immediately

3. What will be the output of this code snippet?

qs = MyModel.objects.filter(active=True)
print(qs.query)
list(qs)
print(qs.query)

medium

A. Data is fetched before printing the first query

B. The SQL query is printed twice, no data fetched

C. The SQL query is printed twice, data fetched on list() call

D. SyntaxError because querysets cannot be printed

Solution

1. Step 1: Understand printing qs.query

   Printing qs.query shows the SQL query string without fetching data.

2. Step 2: Recognize when data is fetched

   Calling list(qs) triggers the database query and fetches data.

3. Final Answer:

   The SQL query is printed twice, data fetched on list() call -> Option C

4. Quick Check:

   Printing query shows SQL, list() fetches data = A [OK]

Hint: Printing qs.query shows SQL, list() triggers fetch [OK]

Common Mistakes:

• Assuming printing qs.query fetches data
• Thinking data is fetched before list()
• Confusing query string with actual data

4. Identify the error in this code that tries to filter a queryset:

qs = MyModel.objects.filter(name='Bob')
qs = qs.filter(age>30)

medium

A. Using > instead of __gt for filtering

B. Chaining filter calls is not allowed

C. Missing parentheses in filter method

D. Filter method should be called on MyModel, not qs

Solution

1. Step 1: Check filter syntax

   Django uses double underscores for lookups like greater than: age__gt=30.

2. Step 2: Identify the incorrect operator

   The code uses > which is invalid in filter keyword arguments.

3. Final Answer:

   Using > instead of __gt for filtering -> Option A

4. Quick Check:

   Use __gt for greater than in filters = C [OK]

Hint: Use __gt, __lt for comparisons in filters [OK]

Common Mistakes:

• Using > instead of __gt in filter
• Thinking filter can't be chained
• Calling filter on model instead of queryset

5. You want to build a queryset that filters users who are active and have logged in within the last 7 days, but you want to add more filters later without hitting the database multiple times. How should you do this?

hard

A. Chain multiple filter() calls on the queryset before evaluating it

B. Call list() after each filter() to fetch data early

C. Use get() to fetch one user and then filter in Python

D. Create separate querysets for each filter and combine results in Python

Solution

1. Step 1: Understand queryset chaining

   Querysets can be chained with multiple filter() calls to build complex queries lazily.

2. Step 2: Avoid early evaluation

   Calling list() or other evaluation methods too early fetches data multiple times, which is inefficient.

3. Final Answer:

   Chain multiple filter() calls on the queryset before evaluating it -> Option A

4. Quick Check:

   Chain filters lazily, evaluate once = B [OK]

Hint: Chain filters, evaluate once to save queries [OK]

Common Mistakes:

• Fetching data early with list() after each filter
• Using get() which fetches single object immediately
• Combining querysets in Python instead of database