I’m struggling with the same here. But I can show you what I’ve got doing some research. Basically, you first start adding the page @Output event in the foo.template.ts: <md-paginator #paginator [length]=”length” [pageIndex]=”pageIndex” [pageSize]=”pageSize” [pageSizeOptions]=”[5, 10, 25, 100]” (page)=”pageEvent = getServerData($event)” > </md-paginator> And later, you have to add the pageEvent attribute in the foo.component.ts … Read more
Use offset = (page – 1) * itemsPerPage + 1.
I’ve implemented pagination in pure React JS recently. Here is a working demo: http://codepen.io/PiotrBerebecki/pen/pEYPbY You would of course have to adjust the logic and the way page numbers are displayed so that it meets your requirements. Full code: class TodoApp extends React.Component { constructor() { super(); this.state = { todos: [‘a’,’b’,’c’,’d’,’e’,’f’,’g’,’h’,’i’,’j’,’k’], currentPage: 1, todosPerPage: 3 … Read more
For that you need to have server side change also. Server will accept fromIndex and batchSize in the API url as query param. let listUrlString = “http://bla.com/json2.php?listType=” + listType + “&t=” + NSUUID().UUIDString + “&batchSize=” + batchSize + “&fromIndex=” + fromIndex In the server response, there will be an extra key totalItems. This will be … Read more
Mongodb 3.4 has introduced $facet aggregation which processes multiple aggregation pipelines within a single stage on the same set of input documents. Using $facet and $group you can find documents with $limit and can get total count. You can use below aggregation in mongodb 3.4 db.collection.aggregate([ { “$facet”: { “totalData”: [ { “$match”: { }}, … Read more
will_paginate 3.0 is designed to take advantage of the new ActiveRecord::Relation in Rails 3, so it defines paginate only on relations by default. It can still work with an array, but you have to tell rails to require that part. In a file in your config/initializers (I used will_paginate_array_fix.rb), add this require ‘will_paginate/array’ Then you … Read more
I thought the custom tags proposed were too complex, this is what I did in the template: <a href=”https://stackoverflow.com/questions/2047622/?{% url_replace request”page’ paginator.next_page_number %}”> And the tag function: @register.simple_tag def url_replace(request, field, value): dict_ = request.GET.copy() dict_[field] = value return dict_.urlencode() If the url_param is not yet in the url, it will be added with value. … Read more
This is a mix of HTML and code but it’s pretty basic, easy to understand and should be fairly simple to decouple to suit your needs I think. try { // Find out how many items are in the table $total = $dbh->query(‘ SELECT COUNT(*) FROM table ‘)->fetchColumn(); // How many items to list per … Read more
In my case, the <mat-paginator> element was inside a container that had an *ngIf on it, which did not render until the data loaded asynchronously. This causes this.paginator to be undefined even in ngAfterViewInit. This causes it to silently fail as MatTableDataSource has no problem with you setting paginator to undefined. The solution was to … Read more
I had the same problem. I used subList: final int start = (int)pageable.getOffset(); final int end = Math.min((start + pageable.getPageSize()), users.size()); final Page<User> page = new PageImpl<>(users.subList(start, end), pageable, users.size());