Pagination ke raba babbar jerin sakamakon zuwa nisa tsari, don kada ka load jiya jiya na rikodan a gida daya. Yana da mahimmanci ga iko da amfani. Django yana ba da ajin Paginator don templates/views, kuma DRF yana ba da pagination na gida-gida ga APIs.
# ❌ loading everything — slow, memory-heavy, bad UX with thousands of rows
articles = Article.objects.()
from django.core.paginator import Paginator
def article_list(request):
articles = Article.objects.all().order_by("-created_at") # ORDER matters for consistent pages
paginator = Paginator(articles, 20) # 20 items per page
page_number = request.GET.get("page") # ?page=2
page_obj = paginator.get_page(page_number) # the requested page
return render(request, "list.html", {"page_obj": page_obj})
<!-- in the template -->
{% for article in page_obj %}
<h2>{{ article.title }}</h2>
{% endfor %}
{% if page_obj.has_previous %}<a href="?page={{ page_obj.previous_page_number }}">Prev</a>{% endif %}
Page {{ page_obj.number }} of {{ page_obj.paginator.num_pages }}
{% if page_obj.has_next %}<a href="?page={{ page_obj.next_page_number }}">Next</a>{% endif %}
The Paginator ke yanke queryset zuwa shafuka kuma get_page() yana dawo da shafar abu mai taimakon kogwaye (has_next, next_page_number, jne.) — lura da shi yana ƙara LIMIT/OFFSET ga bubuiwa, don haka shafa ɗaya ne kawai aka bugi daga jajiya.
# global default in settings.py
REST_FRAMEWORK = {
"DEFAULT_PAGINATION_CLASS": "rest_framework.pagination.PageNumberPagination",
"PAGE_SIZE": 20,
}
# now list endpoints are automatically paginated, returning:
# { "count": 1000, "next": "...?page=3", "previous": "...?page=1", "results": [...] }
DRF yana yin pagination na shafukan jerin jiya a jida da aka sada, yana dawo da metadata shafa (jijiya, na gab da nisa hanya) tare da sakamakon — masu amfani suna juriya ta hanyoyi da aka samar.
PageNumberPagination → ?page=2 (simple page numbers)
LimitOffsetPagination → ?limit=20&offset=40 (flexible offsets)
CursorPagination → opaque cursor; consistent & performant for large/changing data
(avoids OFFSET performance issues on huge datasets)
⚠️ OFFSET-based pagination (page/offset) gets SLOWER on deep pages of huge tables
(the DB must skip OFFSET rows). For very large datasets, CURSOR pagination
(keyset, using a WHERE on an indexed column) is far more efficient.
⚠️ Always ORDER BY a stable field, or pages can be inconsistent/repeat items.
Pagination yana da mahimmanci don gina jira mai iko, masu amfani jira da ke cutar ainihin kwatanonin data — ba tare da shi, jerin shafukan da suke lodar jiya jiya na tebur (watakila dubu ko miliyana jiya) za su zama jiya, kumandisu, da ba sa amfani, dukansu suna damje jajiya da tsanyaya masu amfani da abokan ciniki. "],Saniya pagination shine ilimi na aiki na kowane rana: Django's Paginator yana cutar traditional views/templates (yanke querysets zuwa shafuka tare da taimakon kogwaye, ida ka cutar ƙayyadewa ga LIMIT/OFFSET), da DRF's built-in pagination yana cutar APIs (jida jija pagination a jiya jiya na shafukan tare da metadata da hanyoyi da aka samar) — dukansu ana bukatar su dangane da ko kun gina safo da aka yi jiya ko APIs.
Saniya kaida ce don aiwatar pagination a gidan jiya shine dole a kusan kowane iri na kadarar jerin.
The performance nuance yana da mahimmanci na ajina-ajina ilimi: standard OFFSET-based pagination yana raunin jiya da zurfin shafuka na babbar tebur (jajiya dole ta tsallaki jiya duk da gida), don haka cursor (keyset) pagination yana da mahimmanci don babba ko mabagajiya jajiya, da kuma koda ordering ta ajiya aljihun yana dole don tso rashin jaci ko karawa a shafukan.
Saniya dukansu kira ne (Paginator, DRF pagination classes) da wadannan ikon dangane (OFFSET da cursor pagination, jaci ordering) yana mahimmanci don gina jira da ke zama jiya kuma daidai yayin da data ke girma — pagination yana da mahimmanci a komi, kuma yin ta kyau, musamman a skarwa, yana ilimi na aiki da yake kai tasiri ga jira iko da karanin mai amfani.