paginator.txt 7.5 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220
  1. =========
  2. Paginator
  3. =========
  4. Django provides a few classes that help you manage paginated data -- that is,
  5. data that's split across several pages, with "Previous/Next" links. These
  6. classes live in :source:`django/core/paginator.py`.
  7. For examples, see the :doc:`Pagination topic guide </topics/pagination>`.
  8. .. module:: django.core.paginator
  9. :synopsis: Classes to help you easily manage paginated data.
  10. ``Paginator`` class
  11. ===================
  12. .. class:: Paginator(object_list, per_page, orphans=0, allow_empty_first_page=True)
  13. A paginator acts like a sequence of :class:`Page` when using ``len()`` or
  14. iterating it directly.
  15. .. attribute:: Paginator.object_list
  16. Required. A list, tuple, ``QuerySet``, or other sliceable object with a
  17. ``count()`` or ``__len__()`` method. For consistent pagination,
  18. ``QuerySet``\s should be ordered, e.g. with an
  19. :meth:`~django.db.models.query.QuerySet.order_by` clause or with a default
  20. :attr:`~django.db.models.Options.ordering` on the model.
  21. .. admonition:: Performance issues paginating large ``QuerySet``\s
  22. If you're using a ``QuerySet`` with a very large number of items,
  23. requesting high page numbers might be slow on some databases, because
  24. the resulting ``LIMIT``/``OFFSET`` query needs to count the number of
  25. ``OFFSET`` records which takes longer as the page number gets higher.
  26. .. attribute:: Paginator.per_page
  27. Required. The maximum number of items to include on a page, not including
  28. orphans (see the :attr:`~Paginator.orphans` optional argument below).
  29. .. attribute:: Paginator.orphans
  30. Optional. Use this when you don't want to have a last page with very few
  31. items. If the last page would normally have a number of items less than or
  32. equal to ``orphans``, then those items will be added to the previous page
  33. (which becomes the last page) instead of leaving the items on a page by
  34. themselves. For example, with 23 items, ``per_page=10``, and ``orphans=3``,
  35. there will be two pages; the first page with 10 items and the second
  36. (and last) page with 13 items. ``orphans`` defaults to zero, which means
  37. pages are never combined and the last page may have one item.
  38. .. attribute:: Paginator.allow_empty_first_page
  39. Optional. Whether or not the first page is allowed to be empty. If
  40. ``False`` and ``object_list`` is empty, then an ``EmptyPage`` error will
  41. be raised.
  42. Methods
  43. -------
  44. .. method:: Paginator.get_page(number)
  45. Returns a :class:`Page` object with the given 1-based index, while also
  46. handling out of range and invalid page numbers.
  47. If the page isn't a number, it returns the first page. If the page number
  48. is negative or greater than the number of pages, it returns the last page.
  49. Raises an :exc:`EmptyPage` exception only if you specify
  50. ``Paginator(..., allow_empty_first_page=False)`` and the ``object_list`` is
  51. empty.
  52. .. method:: Paginator.page(number)
  53. Returns a :class:`Page` object with the given 1-based index. Raises
  54. :exc:`PageNotAnInteger` if the ``number`` cannot be converted to an integer
  55. by calling ``int()``. Raises :exc:`EmptyPage` if the given page number
  56. doesn't exist.
  57. .. method:: Paginator.get_elided_page_range(number, *, on_each_side=3, on_ends=2)
  58. Returns a 1-based list of page numbers similar to
  59. :attr:`Paginator.page_range`, but may add an ellipsis to either or both
  60. sides of the current page number when :attr:`Paginator.num_pages` is large.
  61. The number of pages to include on each side of the current page number is
  62. determined by the ``on_each_side`` argument which defaults to 3.
  63. The number of pages to include at the beginning and end of page range is
  64. determined by the ``on_ends`` argument which defaults to 2.
  65. For example, with the default values for ``on_each_side`` and ``on_ends``,
  66. if the current page is 10 and there are 50 pages, the page range will be
  67. ``[1, 2, '…', 7, 8, 9, 10, 11, 12, 13, '…', 49, 50]``. This will result in
  68. pages 7, 8, and 9 to the left of and 11, 12, and 13 to the right of the
  69. current page as well as pages 1 and 2 at the start and 49 and 50 at the
  70. end.
  71. Raises :exc:`InvalidPage` if the given page number doesn't exist.
  72. Attributes
  73. ----------
  74. .. attribute:: Paginator.ELLIPSIS
  75. A translatable string used as a substitute for elided page numbers in the
  76. page range returned by :meth:`~Paginator.get_elided_page_range`. Default is
  77. ``'…'``.
  78. .. attribute:: Paginator.count
  79. The total number of objects, across all pages.
  80. .. note::
  81. When determining the number of objects contained in ``object_list``,
  82. ``Paginator`` will first try calling ``object_list.count()``. If
  83. ``object_list`` has no ``count()`` method, then ``Paginator`` will
  84. fall back to using ``len(object_list)``. This allows objects, such as
  85. ``QuerySet``, to use a more efficient ``count()`` method when
  86. available.
  87. .. attribute:: Paginator.num_pages
  88. The total number of pages.
  89. .. attribute:: Paginator.page_range
  90. A 1-based range iterator of page numbers, e.g. yielding ``[1, 2, 3, 4]``.
  91. ``Page`` class
  92. ==============
  93. You usually won't construct ``Page`` objects by hand -- you'll get them by
  94. iterating :class:`Paginator`, or by using :meth:`Paginator.page`.
  95. .. class:: Page(object_list, number, paginator)
  96. A page acts like a sequence of :attr:`Page.object_list` when using
  97. ``len()`` or iterating it directly.
  98. Methods
  99. -------
  100. .. method:: Page.has_next()
  101. Returns ``True`` if there's a next page.
  102. .. method:: Page.has_previous()
  103. Returns ``True`` if there's a previous page.
  104. .. method:: Page.has_other_pages()
  105. Returns ``True`` if there's a next **or** previous page.
  106. .. method:: Page.next_page_number()
  107. Returns the next page number. Raises :exc:`InvalidPage` if next page
  108. doesn't exist.
  109. .. method:: Page.previous_page_number()
  110. Returns the previous page number. Raises :exc:`InvalidPage` if previous
  111. page doesn't exist.
  112. .. method:: Page.start_index()
  113. Returns the 1-based index of the first object on the page, relative to all
  114. of the objects in the paginator's list. For example, when paginating a list
  115. of 5 objects with 2 objects per page, the second page's
  116. :meth:`~Page.start_index` would return ``3``.
  117. .. method:: Page.end_index()
  118. Returns the 1-based index of the last object on the page, relative to all
  119. of the objects in the paginator's list. For example, when paginating a list
  120. of 5 objects with 2 objects per page, the second page's
  121. :meth:`~Page.end_index` would return ``4``.
  122. Attributes
  123. ----------
  124. .. attribute:: Page.object_list
  125. The list of objects on this page.
  126. .. attribute:: Page.number
  127. The 1-based page number for this page.
  128. .. attribute:: Page.paginator
  129. The associated :class:`Paginator` object.
  130. Exceptions
  131. ==========
  132. .. exception:: InvalidPage
  133. A base class for exceptions raised when a paginator is passed an invalid
  134. page number.
  135. The :meth:`Paginator.page` method raises an exception if the requested page is
  136. invalid (i.e. not an integer) or contains no objects. Generally, it's enough
  137. to catch the ``InvalidPage`` exception, but if you'd like more granularity,
  138. you can catch either of the following exceptions:
  139. .. exception:: PageNotAnInteger
  140. Raised when :meth:`~Paginator.page` is given a value that isn't an integer.
  141. .. exception:: EmptyPage
  142. Raised when :meth:`~Paginator.page` is given a valid value but no objects
  143. exist on that page.
  144. Both of the exceptions are subclasses of :exc:`InvalidPage`, so you can handle
  145. them both with ``except InvalidPage``.