Pagination nembakaké set hasile gedhe dadi kaca-kaca tartamtu, supaya ora muatan rolas rekor sasat-sapisan. Iku penting banget kanggo performance lan usability. Django nyediyakaké class Paginator kanggo template/view, lan DRF nawakake pagination built-in kanggo API.
# ❌ 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 %}
Paginator iku ngumplok queryset dadi kaca-kaca lan get_page() bali obyek kaca sing duwe helper navigasi (has_next, next_page_number, etc.) — iku nambahake LIMIT/OFFSET ing query, dadi cuma siji kaca sing dijupuk saka database.
# 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 muatan halaman endpoint list kanthi otomatis néndi wae dikonfigurasi, mbalik metadata kaca (count, next/previous link) sapirengane hasil — client navigasi via URL sing disediyakaké.
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 iku essential kanggo nggawe aplikasi sing performan lan usable sing nangani data volume nyata — tanpa iku, listing endpoint lan kaca sing muatan tabel lengkap (bisa rolas utawa jutaan baris) dadi alon, ngonsumsi memori, lan ora usable, loro-loro nerasi database lan ndadek user lan client overwhelm.
Ngubengi pagination iku pengetahuan praktis araw-araw: Django Paginator nangani traditional view/template (ngumplok queryset dadi kaca sing duwe helper navigasi, njupuk kanthi efisien cuma siji kaca via LIMIT/OFFSET), lan DRF built-in pagination nangani API (kanthi otomatis muatan endpoint list sing duwe metadata lan navigasi link néndi wae dikonfigurasi) — rong-rorone diperlu gumantung apa sampeyan gawe kaca server-rendered utawa API.
Ngubengi cara nggawe pagination ing loro konteks iku perlu kanggo meh kabeh fitur listing data.
Nuansa performance iku nomer-nomer pengetahuan senior-level: standard OFFSET-based pagination isin ing kaca jero saka tabel gedhe banget (database kudu skip kabeh baris sadurunge), mulane cursor (keyset) pagination iku pilihan efisien kanggo dataset gedhe utawa gantis gancang, lan tansah ordering by stable field iku perlu supaya ora inconsistent utawa baris duplikat ing sadawaning kaca.
Ngubengi dasar mekanik (Paginator, DRF pagination class) lan consideration performance iki (OFFSET vs cursor pagination, ordering konsisten) iku penting kanggo nggawe aplikasi sing tetap cepet lan bener nalika data tuwuh — pagination iku requirement universal, lan ndadakaké nang becik, utamane scale, iku skill praktis sing langsung nagaruhi performance aplikasi lan user experience.