Ordering and slicing querysets in Django - Cheat Sheet & Quick Revision

Recall & Review

beginner

What does the order_by() method do in a Django queryset?

The order_by() method sorts the queryset results based on one or more model fields. You can specify ascending order by field name or descending order by prefixing the field name with a minus sign (-).

beginner

How do you get the first 5 records from a Django queryset?

You use slicing syntax like queryset[:5]. This limits the queryset to the first 5 records, similar to how you slice a list in Python.

intermediate

What happens if you chain order_by() multiple times on a queryset?

Only the last order_by() call takes effect. It overrides any previous ordering specified in earlier calls.

intermediate

Explain how negative slicing works on Django querysets.

Negative slicing like queryset[:-3] is not supported in Django querysets and will raise an error. You can only slice with positive start and stop indexes.

intermediate

How can you order a queryset by multiple fields?

Pass multiple field names to order_by() separated by commas, like order_by('field1', '-field2'). The queryset is ordered by the first field, then by the second field as a tiebreaker.

What does MyModel.objects.all().order_by('-created_at') do?

A Orders results by created_at descending

B Returns unordered results

C Filters results where created_at is negative

D Orders results by created_at ascending

The minus sign (-) before 'created_at' means descending order.

Which of these is the correct way to get the first 10 records from a queryset?

A queryset[1:10]

B queryset[10:]

C queryset[:10]

D queryset[-10:]

Slicing with [:10] returns the first 10 records.

What happens if you call order_by('name').order_by('age') on a queryset?

A Orders by name then age

B Orders by age only

C Orders by name only

D Raises an error

The last order_by call overrides the previous one.

Is negative slicing like queryset[:-5] allowed in Django querysets?

A Yes, but only if queryset is ordered

B Yes, it returns all but last 5 records

C Yes, but only on PostgreSQL

D No, it raises an error

Negative slicing is not supported and causes an error.

How do you order a queryset by 'last_name' ascending and then 'first_name' descending?

A order_by('last_name', '-first_name')

B order_by('-last_name', '-first_name')

C order_by('last_name', 'first_name')

D order_by('-first_name', 'last_name')

Pass multiple fields with '-' prefix for descending order.

Describe how to order a Django queryset by multiple fields and then slice it to get a subset of results.

Think about chaining order_by and slicing like list operations.

Explain why negative slicing is not supported on Django querysets and how you can work around it.

Consider how querysets translate to database queries.

Practice

1. What does the Django queryset method order_by('name') do?

easy

A. Groups the queryset results by the 'name' field.

B. Filters the queryset to only include objects with the name 'order_by'.

C. Sorts the queryset results by the 'name' field in ascending order.

D. Deletes all objects that have a 'name' field.

Solution

1. Step 1: Understand the order_by() method

   The order_by() method sorts the queryset results based on the given field(s).

2. Step 2: Apply order_by('name')

   This sorts the results by the 'name' field in ascending order by default.

3. Final Answer:

   Sorts the queryset results by the 'name' field in ascending order. -> Option C

4. Quick Check:

   order_by('name') = sorted by name ascending [OK]

Hint: Remember: order_by sorts, does not filter or delete [OK]

Common Mistakes:

• Confusing order_by with filter
• Thinking order_by deletes data
• Assuming order_by groups data

2. Which of the following is the correct syntax to get the first 5 objects ordered by 'created_at' descending?

easy

A. Model.objects.order_by('-created_at')[:5]

B. Model.objects[:5].order_by('-created_at')

C. Model.objects.order_by('created_at')[:5]

D. Model.objects.order_by('created_at')[-5:]

Solution

1. Step 1: Use order_by('-created_at') for descending order

   Prefixing the field with '-' sorts descending.

2. Step 2: Slice the queryset with [:5] to get first 5 results

   Slicing before evaluation limits results to first 5.

3. Final Answer:

   Model.objects.order_by('-created_at')[:5] -> Option A

4. Quick Check:

   Descending order + first 5 = order_by('-field')[:5] [OK]

Hint: Use '-' before field for descending order, slice after ordering [OK]

Common Mistakes:

• Slicing before ordering (wrong order)
• Missing '-' for descending order
• Using negative slice like [-5:] incorrectly

3. Given the queryset qs = Model.objects.order_by('age')[2:5], what will list(qs) return if the ages in the database are [20, 25, 30, 35, 40, 45]?

medium

A. [25, 30, 35]

B. [30, 35, 40]

C. [35, 40, 45]

D. [20, 25, 30]

Solution

1. Step 1: Order the ages ascending

   Ordering by 'age' gives [20, 25, 30, 35, 40, 45].

2. Step 2: Slice from index 2 to 5 (excluding 5)

   Indexes 2, 3, 4 correspond to ages 30, 35, 40.

3. Final Answer:

   [30, 35, 40] -> Option B

4. Quick Check:

   order_by + slice = [30, 35, 40] [OK]

Hint: Remember slicing excludes the end index [OK]

Common Mistakes:

• Including the end index in slice
• Mixing up ascending and descending order
• Using wrong slice indexes

4. What is wrong with this queryset code?

qs = Model.objects[:5].order_by('name')

medium

A. You cannot slice a queryset before ordering; slicing must come after ordering.

B. The queryset must be filtered before ordering.

C. The order_by method requires a list, not a string.

D. Slicing with [:5] returns a list, so order_by cannot be called after.

Solution

1. Step 1: Understand queryset slicing returns a list

   Slicing a queryset like Model.objects[:5] evaluates it and returns a list, not a queryset.

2. Step 2: Calling order_by on a list causes error

   Lists do not have order_by method, so this code raises an error.

3. Final Answer:

   Slicing with [:5] returns a list, so order_by cannot be called after. -> Option D

4. Quick Check:

   Slice first = list, no order_by after [OK]

Hint: Always order before slicing to keep queryset chainable [OK]

Common Mistakes:

• Slicing before ordering
• Thinking order_by accepts lists
• Confusing filter and order_by order

5. You want to get the 3rd to 7th newest entries from a model ordered by 'published_date' descending. Which queryset code is correct?

hard

A. Model.objects.order_by('-published_date')[2:7]

B. Model.objects.order_by('published_date')[3:8]

C. Model.objects[2:7].order_by('-published_date')

D. Model.objects.order_by('-published_date')[3:8]

Solution

1. Step 1: Order by 'published_date' descending

   Use order_by('-published_date') to get newest first.

2. Step 2: Slice from index 2 to 7 to get 3rd to 7th entries

   Slicing [2:7] gets items at indexes 2,3,4,5,6 (5 items total).

3. Final Answer:

   Model.objects.order_by('-published_date')[2:7] -> Option A

4. Quick Check:

   Descending order + slice 2:7 = 3rd to 7th newest [OK]

Hint: Order descending first, then slice with zero-based indexes [OK]

Common Mistakes:

• Using ascending order instead of descending
• Slicing with wrong indexes (off by one)
• Slicing before ordering