Ordering and slicing help you get data from the database in the order and amount you want. This makes your app faster and easier to use.
Ordering and slicing querysets in Django
Model.objects.order_by('field_name')[start:end]Use order_by() to sort results by one or more fields.
Use slicing [start:end] to get a subset of results, like a list slice.
Book.objects.order_by('title')Book.objects.order_by('-published_date')Book.objects.order_by('author')[0:5]
Book.objects.all()[10:20]
This example shows how to get books sorted by newest published date first, then take only the first two books from that list. It prints their title, author, and date.
from django.db import models class Book(models.Model): title = models.CharField(max_length=100) author = models.CharField(max_length=100) published_date = models.DateField() # Imagine we have these books in the database: # 1. Title: 'A Tale of Two Cities', Author: 'Charles Dickens', Date: 1859-04-30 # 2. Title: 'Moby Dick', Author: 'Herman Melville', Date: 1851-10-18 # 3. Title: 'Pride and Prejudice', Author: 'Jane Austen', Date: 1813-01-28 # Get books ordered by published_date descending (newest first) books = Book.objects.order_by('-published_date') # Get the first 2 books from this ordered list top_two_books = books[:2] for book in top_two_books: print(f"{book.title} by {book.author} ({book.published_date})")
Slicing querysets uses zero-based indexing like Python lists.
Ordering by multiple fields is possible: .order_by('field1', '-field2').
Negative sign - before field name means descending order.
Use order_by() to sort your data by one or more fields.
Use slicing [start:end] to get only part of the data.
Ordering and slicing together help you show data in the right order and amount.
Practice
order_by('name') do?Solution
Step 1: Understand the
Theorder_by()methodorder_by()method sorts the queryset results based on the given field(s).Step 2: Apply
This sorts the results by the 'name' field in ascending order by default.order_by('name')Final Answer:
Sorts the queryset results by the 'name' field in ascending order. -> Option CQuick Check:
order_by('name') = sorted by name ascending [OK]
- Confusing order_by with filter
- Thinking order_by deletes data
- Assuming order_by groups data
Solution
Step 1: Use
Prefixing the field with '-' sorts descending.order_by('-created_at')for descending orderStep 2: Slice the queryset with
Slicing before evaluation limits results to first 5.[:5]to get first 5 resultsFinal Answer:
Model.objects.order_by('-created_at')[:5] -> Option AQuick Check:
Descending order + first 5 = order_by('-field')[:5] [OK]
- Slicing before ordering (wrong order)
- Missing '-' for descending order
- Using negative slice like [-5:] incorrectly
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]?Solution
Step 1: Order the ages ascending
Ordering by 'age' gives [20, 25, 30, 35, 40, 45].Step 2: Slice from index 2 to 5 (excluding 5)
Indexes 2, 3, 4 correspond to ages 30, 35, 40.Final Answer:
[30, 35, 40] -> Option BQuick Check:
order_by + slice = [30, 35, 40] [OK]
- Including the end index in slice
- Mixing up ascending and descending order
- Using wrong slice indexes
qs = Model.objects[:5].order_by('name')Solution
Step 1: Understand queryset slicing returns a list
Slicing a queryset likeModel.objects[:5]evaluates it and returns a list, not a queryset.Step 2: Calling
Lists do not haveorder_byon a list causes errororder_bymethod, so this code raises an error.Final Answer:
Slicing with [:5] returns a list, so order_by cannot be called after. -> Option DQuick Check:
Slice first = list, no order_by after [OK]
- Slicing before ordering
- Thinking order_by accepts lists
- Confusing filter and order_by order
Solution
Step 1: Order by 'published_date' descending
Useorder_by('-published_date')to get newest first.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).Final Answer:
Model.objects.order_by('-published_date')[2:7] -> Option AQuick Check:
Descending order + slice 2:7 = 3rd to 7th newest [OK]
- Using ascending order instead of descending
- Slicing with wrong indexes (off by one)
- Slicing before ordering
Ready to prove it?
Pass the test and this pattern moves unknown
