Why Pagination (PageNumber, Cursor, Limit/Offset) in Django? - Purpose & Use Cases

The Big Idea

Discover how a simple tool can make your website feel lightning fast even with tons of data!

The Scenario

Imagine you have a website showing hundreds of products all at once on one page. You try to load them manually by fetching all data and displaying it together.

The Problem

Loading all items at once makes the page slow and heavy. Users wait too long, and the browser might freeze. Also, manually slicing data for pages is tricky and error-prone.

The Solution

Pagination in Django helps split data into small, easy-to-load pages automatically. It manages page numbers, cursors, or limits behind the scenes so users get fast, smooth browsing.

Before vs After

✗ Before

all_items = Product.objects.all()
# manually slice items for page
page_items = all_items[20:40]

✓ After

from django.core.paginator import Paginator
paginator = Paginator(Product.objects.all(), 20)
page_items = paginator.get_page(2)

What It Enables

It enables fast, user-friendly browsing of large data sets by loading only what is needed per page.

Real Life Example

Online stores show 20 products per page instead of hundreds, letting shoppers browse quickly without waiting.

Key Takeaways

Manual loading of all data is slow and overwhelming.

Django pagination splits data into manageable pages automatically.

This improves speed, user experience, and reduces errors.

Practice

1. Which Django REST Framework pagination style uses a page number to fetch specific pages of data?

easy

A. PageNumberPagination

B. CursorPagination

C. LimitOffsetPagination

D. OffsetPagination

Solution

1. Step 1: Understand pagination styles

   PageNumberPagination uses page numbers like 1, 2, 3 to get data pages.

2. Step 2: Match style to description

   CursorPagination uses a cursor token, LimitOffsetPagination uses limit and offset numbers, so they don't use page numbers.

3. Final Answer:

   PageNumberPagination -> Option A

4. Quick Check:

   Page number style = PageNumberPagination [OK]

Hint: PageNumberPagination uses simple page numbers like 1, 2, 3 [OK]

Common Mistakes:

• Confusing CursorPagination with page numbers
• Thinking LimitOffsetPagination uses page numbers
• Assuming OffsetPagination is a valid DRF style

2. Which of the following is the correct way to set LimitOffsetPagination in Django REST Framework settings?

easy

A. "DEFAULT_PAGINATION_CLASS": "rest_framework.pagination.OffsetPagination"

B. "DEFAULT_PAGINATION_CLASS": "rest_framework.pagination.PageNumberPagination"

C. "DEFAULT_PAGINATION_CLASS": "rest_framework.pagination.LimitOffsetPagination"

D. "DEFAULT_PAGINATION_CLASS": "rest_framework.pagination.CursorPagination"

Solution

1. Step 1: Identify correct class path

   LimitOffsetPagination is located at rest_framework.pagination.LimitOffsetPagination.

2. Step 2: Verify syntax for settings

   The setting key is DEFAULT_PAGINATION_CLASS and the value is the full class path as a string.

3. Final Answer:

   "DEFAULT_PAGINATION_CLASS": "rest_framework.pagination.LimitOffsetPagination" -> Option C

4. Quick Check:

   Correct class path and setting key = "DEFAULT_PAGINATION_CLASS": "rest_framework.pagination.LimitOffsetPagination" [OK]

Hint: Use full class path string for pagination in settings [OK]

Common Mistakes:

• Using OffsetPagination which does not exist
• Missing quotes around class path string
• Mixing pagination class names

3. Given this code snippet using CursorPagination, what will be the value of the next cursor if the current cursor is 'abc123' and page size is 2?

class MyCursorPagination(CursorPagination):
    page_size = 2

paginator = MyCursorPagination()
next_cursor = paginator.get_next_link()

medium

A. A tuple with offset and limit values

B. An integer representing the next page number

C. None, because get_next_link() returns nothing

D. A URL containing a cursor parameter with a new encoded cursor

Solution

1. Step 1: Understand CursorPagination behavior

   CursorPagination returns URLs with encoded cursor tokens for next pages, not page numbers or tuples.

2. Step 2: Analyze get_next_link() output

   get_next_link() returns a URL string containing the next cursor parameter for pagination.

3. Final Answer:

   A URL containing a cursor parameter with a new encoded cursor -> Option D

4. Quick Check:

   CursorPagination next link = URL with cursor [OK]

Hint: CursorPagination returns URLs with cursor tokens, not numbers [OK]

Common Mistakes:

• Expecting page numbers from CursorPagination
• Thinking get_next_link() returns None
• Confusing limit/offset with cursor

4. You have this Django REST Framework view using LimitOffsetPagination but it raises an error:

class MyLimitOffsetPagination(LimitOffsetPagination):
    default_limit = '10'

class MyView(ListAPIView):
    pagination_class = MyLimitOffsetPagination
    queryset = MyModel.objects.all()
    serializer_class = MySerializer

What is the likely cause of the error?

medium

A. pagination_class should be a string path, not a class

B. default_limit should be an integer, not a string

C. ListAPIView does not support pagination

D. queryset must be a list, not a QuerySet

Solution

1. Step 1: Check default_limit type

   default_limit must be an integer, but it is set as a string '10', causing a type error.

2. Step 2: Verify other parts

   pagination_class can be a class, ListAPIView supports pagination, queryset can be a QuerySet.

3. Final Answer:

   default_limit should be an integer, not a string -> Option B

4. Quick Check:

   default_limit type error = default_limit should be an integer, not a string [OK]

Hint: default_limit must be int, not quoted string [OK]

Common Mistakes:

• Setting default_limit as string instead of int
• Thinking pagination_class must be string path
• Assuming ListAPIView disables pagination

5. You want to implement pagination for a large dataset where new items are frequently added. Which pagination style is best to avoid duplicate or missing items when users navigate pages?

hard

A. CursorPagination

B. PageNumberPagination

C. LimitOffsetPagination

D. No pagination

Solution

1. Step 1: Understand pagination challenges with dynamic data

   PageNumber and LimitOffset can cause duplicates or missing items if data changes between requests.

2. Step 2: Identify pagination style that handles dynamic data well

   CursorPagination uses a stable cursor based on item order, preventing duplicates or skips when data changes.

3. Final Answer:

   CursorPagination -> Option A

4. Quick Check:

   Dynamic data needs CursorPagination [OK]

Hint: Use CursorPagination for changing data to avoid duplicates [OK]

Common Mistakes:

• Choosing PageNumberPagination for dynamic data
• Thinking LimitOffsetPagination handles data changes well
• Ignoring pagination for large datasets