Laravel 5.4
Awesome Laravel
- Awesome Laravel (Chirag Gude)
Prologue
- Release Notes
- Upgrade Guide
Getting Started
- Installation
- Configuration
- Directory Structure
- Laravel Homestead
- valet
Architecture Concepts
- Request Lifecycle
- Service Container
- Service Providers
- Facades
The Basics
- Routing
- Errors & Logging
- Middleware
- CSRF Protection
- Controllers
- HTTP Requests
- HTTP Responses
- Views
- HTTP Session
- Validation
Frontend
- Blade Templates
- Localization
- JavaScript & CSS Scaffolding
- Compiling Assets (Laravel Mix)
Security
- Authentication
- API Authentication (Passport)
- Authorization
- Encryption
- Hashing
- Resetting Passwords
Digging Deeper
- Artisan Console
- Queues
- Package Development
- Task Scheduling
- Broadcasting
- Cache
- Collections
- Events
- File Storage
- helpers
- Notifications
Database
- Database Getting Started
- Database Query Builder
- Database Pagination
- Database Migrations
- Database Seeding
- Redis
Eloquent ORM
- Eloquent Getting Started
- Eloquent Relationships
- Eloquent Collections
- Eloquent Mutators
- Eloquent Serialization
Testing
- Testing Getting Started
- HTTP Tests
- Browser Tests (Laravel Dusk)
- Database Testing
- Mocking
- redirect
Official Packages
- Laravel Cashier
- Envoy Task Runner
- Laravel Scout
Database Pagination
Introduction
In other frameworks, pagination can be very painful. Laravel’s paginator is integrated with the query builder and Eloquent ORM and provides convenient, easy-to-use pagination of database results out of the box. The HTML generated by the paginator is compatible with the Bootstrap CSS framework.
Basic Usage
Paginating Query Builder Results
There are several ways to paginate items. The simplest is by using the paginate
method on the query builder or an Eloquent query. The paginate
method automatically takes care of setting the proper limit and offset based on the current page being viewed by the user. By default, the current page is detected by the value of the page
query string argument on the HTTP request. Of course, this value is automatically detected by Laravel, and is also automatically inserted into links generated by the paginator.
In this example, the only argument passed to the paginate
method is the number of items you would like displayed “per page”. In this case, let’s specify that we would like to display 15
items per page:
|
{note} Currently, pagination operations that use a
groupBy
statement cannot be executed efficiently by Laravel. If you need to use agroupBy
with a paginated result set, it is recommended that you query the database and create a paginator manually.
“Simple Pagination”
If you only need to display simple “Next” and “Previous” links in your pagination view, you may use the simplePaginate
method to perform a more efficient query. This is very useful for large datasets when you do not need to display a link for each page number when rendering your view:
|
Paginating Eloquent Results
You may also paginate Eloquent queries. In this example, we will paginate the User
model with 15
items per page. As you can see, the syntax is nearly identical to paginating query builder results:
|
Of course, you may call paginate
after setting other constraints on the query, such as where
clauses:
|
You may also use the simplePaginate
method when paginating Eloquent models:
|
Manually Creating A Paginator
Sometimes you may wish to create a pagination instance manually, passing it an array of items. You may do so by creating either an Illuminate\Pagination\Paginator
or Illuminate\Pagination\LengthAwarePaginator
instance, depending on your needs.
The Paginator
class does not need to know the total number of items in the result set; however, because of this, the class does not have methods for retrieving the index of the last page. The LengthAwarePaginator
accepts almost the same arguments as the Paginator
; however, it does require a count of the total number of items in the result set.
In other words, the Paginator
corresponds to the simplePaginate
method on the query builder and Eloquent, while the LengthAwarePaginator
corresponds to the paginate
method.
{note} When manually creating a paginator instance, you should manually “slice” the array of results you pass to the paginator. If you’re unsure how to do this, check out the array_slice PHP function.
Displaying Pagination Results
When calling the paginate
method, you will receive an instance of Illuminate\Pagination\LengthAwarePaginator
. When calling the simplePaginate
method, you will receive an instance of Illuminate\Pagination\Paginator
. These objects provide several methods that describe the result set. In addition to these helpers methods, the paginator instances are iterators and may be looped as an array. So, once you have retrieved the results, you may display the results and render the page links using Blade:
|
The links
method will render the links to the rest of the pages in the result set. Each of these links will already contain the proper page
query string variable. Remember, the HTML generated by the links
method is compatible with the Bootstrap CSS framework.
Customizing The Paginator URI
The withPath
method allows you to customize the URI used by the paginator when generating links. For example, if you want the paginator to generate links like http://example.com/custom/url?page=N
, you should pass custom/url
to the withPath
method:
|
Appending To Pagination Links
You may append to the query string of pagination links using the appends
method. For example, to append sort=votes
to each pagination link, you should make the following call to appends
:
|
If you wish to append a “hash fragment” to the paginator’s URLs, you may use the fragment
method. For example, to append #foo
to the end of each pagination link, make the following call to the fragment
method:
|
Converting Results To JSON
The Laravel paginator result classes implement the Illuminate\Contracts\Support\Jsonable
Interface contract and expose the toJson
method, so it’s very easy to convert your pagination results to JSON. You may also convert a paginator instance to JSON by simply returning it from a route or controller action:
|
The JSON from the paginator will include meta information such as total
, current_page
, last_page
, and more. The actual result objects will be available via the data
key in the JSON array. Here is an example of the JSON created by returning a paginator instance from a route:
|
Customizing The Pagination View
By default, the views rendered to display the pagination links are compatible with the Bootstrap CSS framework. However, if you are not using Bootstrap, you are free to define your own views to render these links. When calling the links
method on a paginator instance, pass the view name as the first argument to the method:
|
However, the easiest way to customize the pagination views is by exporting them to your resources/views/vendor
directory using the vendor:publish
command:
|
This command will place the views in the resources/views/vendor/pagination
directory. The default.blade.php
file within this directory corresponds to the default pagination view. Simply edit this file to modify the pagination HTML.
Paginator Instance Methods
Each paginator instance provides additional pagination information via the following methods:
$results->count()
$results->currentPage()
$results->firstItem()
$results->hasMorePages()
$results->lastItem()
$results->lastPage() (Not available when using simplePaginate)
$results->nextPageUrl()
$results->perPage()
$results->previousPageUrl()
$results->total() (Not available when using simplePaginate)
$results->url($page)