Ordering and slicing querysets in Django - Mini Project: Build & Apply

Ordering and slicing querysets

📖 Scenario: You are building a simple Django app to manage a bookstore's inventory. You want to display books sorted by their publication year and show only a limited number of recent books on the homepage.

🎯 Goal: Learn how to order and slice Django querysets to get sorted and limited data from the database.

📋 What You'll Learn

Create a Django model queryset with book data

Add a variable to specify how many books to show

Order the queryset by publication year descending

Slice the queryset to get only the top N recent books

💡 Why This Matters

🌍 Real World

Ordering and slicing querysets is common when showing sorted lists of items, like recent blog posts, top products, or latest news.

💼 Career

Django developers frequently use queryset ordering and slicing to efficiently fetch and display data in web applications.

1

Create the initial queryset

Create a variable called books that gets all objects from the Book model using Book.objects.all().

Django

# Create the initial queryset for all books
# Your code here

Hint

Use the Django ORM method objects.all() on the Book model to get all books.

2

Add a limit variable

Add a variable called limit and set it to 5 to specify how many books to show.

Django

books = Book.objects.all()
# Set the limit of books to show
# Your code here

Hint

Just create a variable limit and assign it the number 5.

3

Order the queryset by publication year descending

Update the books queryset to order by the publication_year field in descending order using order_by('-publication_year').

Django

books = Book.objects.all()
limit = 5
# Order books by publication_year descending
# Your code here

Hint

Use order_by('-publication_year') to sort from newest to oldest.

4

Slice the queryset to get only the top N recent books

Slice the books queryset to keep only the first limit items using books = books[:limit].

Django

books = Book.objects.all().order_by('-publication_year')
limit = 5
# Slice books to show only the top limit
# Your code here

Hint

Use Python slicing syntax [:limit] on the queryset to limit results.

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