Is there a way to make an `Oracle` query behave like it contains a MySQL `limit` clause?

In MySQL, I can do this:

    select * 
    from sometable
    order by name
    limit 20,10

to get the 21st to the 30th rows (skip the first 20, give the next 10). The rows are selected after the `order by`, so it really starts on the 20th name alphabetically.

In Oracle, the only thing people mention is the `rownum` pseudo-column, but it is evaluated *before* `order by`, which means this:

    select * 
    from sometable
    where rownum &lt;= 10
    order by name

will return a random set of ten rows ordered by name, which is not usually what I want. It also doesn&#39;t allow for specifying an offset.

How do I limit the number of rows returned by an Oracle query after ordering?

I&#39;m making a pagination system (sort of like Facebook) where the content loads when the user scrolls to the bottom. I imagine the best way to do that is to find when the user is at the bottom of the page and run an Ajax query to load more posts.

The only problem is I don&#39;t know how to check if the user has scrolled to the bottom of the page. Any ideas?

I&#39;m using jQuery, so feel free to provide answers that use it.

Check if a user has scrolled to the bottom (not just the window, but any element)

What is the best way (performance wise) to paginate results in SQL Server 2000, 2005, 2008, 2012 if you also want to get the total number of results (before paginating)?

What is the best way to paginate results in SQL Server

This is a more generic reformulation of [this question][1] (with the elimination of the Rails specific parts)

I am not sure how to implement pagination on a resource in a RESTful web application.
Assuming that I have a resource called `products`, which of the following do you think is the best approach, and why:

&lt;h2&gt;1. Using only query strings&lt;/h2&gt;
eg. `http://application/products?page=2&amp;sort_by=date&amp;sort_how=asc`
&lt;br /&gt;The problem here is that I can&#39;t use full page caching and also the URL is not very clean and easy to remember.

&lt;h2&gt;2. Using pages as resources and query strings for sorting&lt;/h2&gt;
eg. `http://application/products/page/2?sort_by=date&amp;sort_how=asc`
&lt;br /&gt;In this case, the problem that is see is that `http://application/products/pages/1` is not a unique resource since using `sort_by=price` can yield a totally different result *and* I still can&#39;t use page caching.

&lt;h2&gt;3. Using pages as resources and an URL segment for sorting&lt;/h2&gt;
eg. `http://application/products/by-date/page/2`
&lt;br /&gt;I personally see no problem in using this method, but someone warned me that this is not a good way to go (he didn&#39;t give a reason, so if you know *why* it&#39;s not recommended, please let me know)

*Any* suggestions, opinions, critiques are more than welcome. Thanks.

  [1]: https://stackoverflow.com/questions/676571/pagination-and-sorting-in-a-rails-restful-application

Pagination in a REST web application

I&#39;d love some some help handling a strange edge case with a paginated API I&#39;m building.

Like many APIs, this one paginates large results. If you query /foos, you&#39;ll get 100 results (i.e. foo #1-100), and a link to /foos?page=2 which should return foo #101-200.

Unfortunately, if foo #10 is deleted from the data set before the API consumer makes the next query, /foos?page=2 will offset by 100 and return foos #102-201.

This is a problem for API consumers who are trying to pull all foos - they will not receive foo #101.

What&#39;s the best practice to handle this? We&#39;d like to make it as lightweight as possible (i.e. avoiding handling sessions for API requests). Examples from other APIs would be greatly appreciated!

API pagination best practices

I am writing a webapp with Node.js and mongoose. How can I paginate the results I get from a `.find()` call? I would like a functionality comparable to `&quot;LIMIT 50,100&quot;` in SQL.

How to paginate with Mongoose in Node.js?

My iPhone application connects to my PHP web service to retrieve data from a MySQL database, a request can return up to 500 results.

What is the best way to implement paging and retrieve 20 items at a time?

Let&#39;s say I receive the first 20 entries from my database, how can I now request the next 20 entries?

MySQL Data - Best way to implement paging?

I have a dataset of about 1000 items in-memory and am attempting to create a pager for
this dataset, but I&#39;m not sure on how to do this.

I&#39;m using a custom filter function to filter the results, and that works fine, but somehow I need to get the number of pages out.

Any clues?

How to do paging in AngularJS?

In PostgreSQL there is the `Limit` and `Offset` keywords which will allow very easy pagination of result sets. 

What is the equivalent syntax for SQL Server? 

Equivalent of LIMIT and OFFSET for SQL Server?

I&#39;m trying to do something like :

    SELECT * FROM table LIMIT 10,20

or

    SELECT * FROM table LIMIT 10 OFFSET 10

but using SQL Server

The only [solution I found][1] looks like overkill:

    SELECT * FROM ( 
      SELECT *, ROW_NUMBER() OVER (ORDER BY name) as row FROM sys.databases 
     ) a WHERE row &gt; 5 and row &lt;= 10

I also [found][2]:

    SELECT TOP 10 * FROM stuff; 

... but it&#39;s not what I want to do since I can&#39;t specify the starting limit.

Is there another way for me to do that ? 

Also, just curious, is there a reason why doesn&#39;t SQL Server support the `LIMIT` function or something similar? I don&#39;t want to be mean, but that really sounds like something a DBMS needs ... If it does, then I&#39;m sorry for being so ignorant! I&#39;ve been working with MySQL and SQL+ for the past 5 years so...


  [1]: http://blogs.msdn.com/sqlserver/archive/2006/10/25/limit-in-sql-server.aspx
  [2]: http://vorg.ca/626-the-MS-SQL-equivalent-to-MySQLs-limit-command

LIMIT 10..20 in SQL Server

I have been trying to understand a little bit about how to implement custom paging in SQL, for instance reading [articles like this one][1].

I have the following query, which works perfectly. But I would like to implement paging with this one.


    SELECT TOP x PostId FROM ( SELECT PostId, MAX (Datemade) as LastDate
     from dbForumEntry 
     group by PostId ) SubQueryAlias
     order by LastDate desc

**What is it I want**

I have forum posts, with related entries. I want to get the posts with the latest added entries, so I can select the recently debated posts.

Now, I want to be able to get the &quot;top 10 to 20 recently active posts&quot;, instead of &quot;top 10&quot;.

**What have I tried**

I have tried to implement the ROW functions as the one in the article, but really with no luck. 

Any ideas how to implement it?

  [1]: https://stackoverflow.com/questions/548475/efficient-way-to-implement-paging

Implement paging (skip / take) functionality with this query

For pagination purposes, I need a run a query with the `LIMIT` and `OFFSET` clauses. But I also need a count of the number of rows that would be returned by that query without the `LIMIT` and `OFFSET` clauses.

I want to run:

    SELECT * FROM table WHERE /* whatever */ ORDER BY col1 LIMIT ? OFFSET ?

And:

    SELECT COUNT(*) FROM table WHERE /* whatever */

At the same time.  Is there a way to do that, particularly a way that lets Postgres optimize it, so that it&#39;s faster than running both individually?

Run a query with a LIMIT/OFFSET and also get the total number of rows

I am using Eloquent together with Laravel 4&#39;s Pagination class.

**Problem:** When there are some GET parameters in the URL, eg: `http://site.com/users?gender=female&amp;body=hot`, the pagination links produced only contain the `page` parameter and nothing else.


**Blade Template**

    {{ $users-&gt;link() }}

There&#39;s a `-&gt;append()` function for this, but when we don&#39;t know how many of the GET parameters are there, how can we use `append()` to include the other GET parameters in the paginated links without a whole chunk of `if` code messing up our blade template?



Laravel Pagination links not including other GET parameters

I&#39;m interested in exposing a direct REST interface to collections of JSON documents (think [CouchDB](http://couchdb.apache.org/) or [Persevere](http://persvr.org/)). The problem I&#39;m running into is how to handle the `GET` operation on the collection root if the collection is large.

As an example pretend I&#39;m exposing StackOverflow&#39;s `Questions` table where each row is exposed as a document (not that there necessarily is such a table, just a concrete example of a sizable collection of &#39;documents&#39;). The collection would be made available at `/db/questions` with the usual CRUD api `GET /db/questions/XXX`, `PUT /db/questions/XXX`, `POST /db/questions` is in play. The standard way to get the entire collection is to `GET /db/questions` but if that naively dumps each row as a JSON object, you&#39;ll get a rather sizeable download and a lot of work on the part of the server. 

The solution is, of course, paging. Dojo has solved this problem in its [JsonRestStore](http://docs.dojocampus.org/dojox/data/JsonRestStore#id7) via a clever RFC2616-compliant extension of using the `Range` header with a custom range unit `items`. The result is a `206 Partial Content` that returns only the requested range. The advantage of this approach over a query parameter is that it leaves the query string for...queries (e.g. `GET /db/questions/?score&gt;200` or somesuch, and yes that&#39;d be encoded `%3E`).

This approach completely covers the behavior I want. The problem is that [RFC 2616](https://www.rfc-editor.org/rfc/rfc2616) specifies that on a 206 response (emphasis mine):

&gt;   The **request** MUST have included a Range header field ([section 14.35](https://www.rfc-editor.org/rfc/rfc2616#section-14.35))
&gt;   indicating the desired range, and MAY have included an If-Range
&gt;   header field ([section 14.27](https://www.rfc-editor.org/rfc/rfc2616#section-14.27)) to make the request conditional.

This makes sense in the context of the standard usage of the header but is a problem because I&#39;d like the 206 response to be the default to handle naive clients/random people exploring.

I&#39;ve gone over the RFC in detail looking for a solution but have been unhappy with my solutions and am interested in SO&#39;s take on the problem. 

Ideas I&#39;ve had:

* *Return `200` with a `Content-Range` header!* - I don&#39;t think that this is wrong, but I&#39;d prefer if a more obvious indicator that the response is only Partial Content.
* *Return `400 Range Required`* - There is not a special 400 response code for required headers, so the default error has to be used and read by hand. This also makes exploration via web browser (or some other client like Resty) more difficult.
* *Use a query parameter* - The standard approach, but I&#39;m hoping to allow queries a la Persevere and this cuts into the query namespace.
* *Just return `206`!* - I think most clients wouldn&#39;t freak out, but I&#39;d rather not go against a MUST in the RFC
* *Extend the spec! Return `266 Partial Content`* - Behaves exactly like 206 but is in response to a request that MUST NOT contain the `Range` header. I figure that 266 is high enough that I shouldn&#39;t run into collision issues and it makes sense to me but I&#39;m not clear on whether this is considered taboo or not.

I&#39;d think this is a fairly common problem and I&#39;d like to see this done in a sort of de facto fashion so I or someone else isn&#39;t reinventing the wheel.

What&#39;s the best way to expose a full collection via HTTP when the collection is large?

Paging in a Rest Collection

I&#39;m trying to add pages to my list. I followed the AngularJS tutorial, the one about smartphones and I&#39;m trying to display only certain number of objects. Here is my html file:

	  &lt;div class=&#39;container-fluid&#39;&gt;
		&lt;div class=&#39;row-fluid&#39;&gt;
			&lt;div class=&#39;span2&#39;&gt;
				Search: &lt;input ng-model=&#39;searchBar&#39;&gt;
				Sort by: 
				&lt;select ng-model=&#39;orderProp&#39;&gt;
					&lt;option value=&#39;name&#39;&gt;Alphabetical&lt;/option&gt;
					&lt;option value=&#39;age&#39;&gt;Newest&lt;/option&gt;
				&lt;/select&gt;
				You selected the phones to be ordered by: {{orderProp}}
			&lt;/div&gt;

			&lt;div class=&#39;span10&#39;&gt;
			  &lt;select ng-model=&#39;limit&#39;&gt;
				&lt;option value=&#39;5&#39;&gt;Show 5 per page&lt;/option&gt;
				&lt;option value=&#39;10&#39;&gt;Show 10 per page&lt;/option&gt;
				&lt;option value=&#39;15&#39;&gt;Show 15 per page&lt;/option&gt;
				&lt;option value=&#39;20&#39;&gt;Show 20 per page&lt;/option&gt;
			  &lt;/select&gt;
			  &lt;ul class=&#39;phones&#39;&gt;
				&lt;li class=&#39;thumbnail&#39; ng-repeat=&#39;phone in phones | filter:searchBar | orderBy:orderProp | limitTo:limit&#39;&gt;
					&lt;a href=&#39;#/phones/{{phone.id}}&#39; class=&#39;thumb&#39;&gt;&lt;img ng-src=&#39;{{phone.imageUrl}}&#39;&gt;&lt;/a&gt;
					&lt;a href=&#39;#/phones/{{phone.id}}&#39;&gt;{{phone.name}}&lt;/a&gt;
					&lt;p&gt;{{phone.snippet}}&lt;/p&gt;
				&lt;/li&gt;
			  &lt;/ul&gt;
			&lt;/div&gt;
		&lt;/div&gt;
	  &lt;/div&gt;

I&#39;ve added a select tag with some values in order to limit the number of items that will be displayed. What I want now is to add the pagination to display the next 5, 10, etc.

I have a controller that works with this:

    function PhoneListCtrl($scope, Phone){
    	$scope.phones = Phone.query();
    	$scope.orderProp = &#39;age&#39;;
    	$scope.limit = 5;
    }

And also I have a module in order to retrieve the data from the json files.

    angular.module(&#39;phonecatServices&#39;, [&#39;ngResource&#39;]).
    	factory(&#39;Phone&#39;, function($resource){
    		return $resource(&#39;phones/:phoneId.json&#39;, {}, {
    			query: {method: &#39;GET&#39;, params:{phoneId:&#39;phones&#39;}, isArray:true}
    		});
    	});

Pagination on a list using ng-repeat

I was wondering if there was a way to get the number of results from a MySQL query, and at the same time limit the results.

The way pagination works (as I understand it), first I do something like

    query = SELECT COUNT(*) FROM `table` WHERE `some_condition`

After I get the num_rows(query), I have the number of results. But then to actually limit my results, I have to do a second query like:

    query2 = SELECT COUNT(*) FROM `table` WHERE `some_condition` LIMIT 0, 10

My question: Is there anyway to both retrieve the total number of results that would be given, AND limit the results returned in a single query? Or any more efficient way of doing this. Thanks!




MySQL pagination without double-querying?

Should I use LINQ&#39;s `Skip()` and `Take()` method for paging, or implement my own paging with a SQL query?

Which is most efficient? Why would I choose one over the other?

I&#39;m using SQL Server 2008, ASP.NET MVC and LINQ.

efficient way to implement paging

For example, I want to populate a gridview control in an ASP.NET web page with only the data necessary for the # of rows displayed. How can NHibernate support this?

How can you do paging with NHibernate?

I am new in jQuery. I have used Datatables in grid but need not pagination. 

There is a list of orders in one page and I show them in a Datatable grid but in bottom I do not  want to show pagination.
Is there any way to remove or hide pagination from the data table by using a bit customization on the jQuery library.

![enter image description here][1]

I tried to customize it but I found very few methods to do it..

Thanks in advance.


  [1]: http://i.stack.imgur.com/q8MSN.png

how to remove pagination in datatable

I am trying to write a Javascript function that takes an `array`, `page_size` and `page_number` as parameters and returns an array that mimics paginated results:

    paginate: function (array, page_size, page_number) {
      return result;
    }

so for example when:

    array = [1, 2, 3, 4, 5],
    page size = 2,
    page_number = 2,

the function should return: `[3, 4]`.

Any ideas would be appreciated.

Paginate Javascript array

I am developing an application that uses SQLite. I want to show a list of users (UITableView) using a paginating mechanism. Could any one please tell me how to load more data in my list when the user scrolls to the end of the list (like on home page on Facebook application)? 

UITableView load more when scrolling to bottom like Facebook application

As a Flask beginner, I can&#39;t understand how `request.args` is used. I read somewhere that it is used to return values of query string (correct me if I&#39;m wrong) and how many parameters `request.args.get()` takes.

I know that when I have to store submitted form data, I can use `fname = request.form.get(&quot;firstname&quot;)`. Here, only one parameter is passed, whereas the code below takes two parameters.
    
    @app.route(&quot;/&quot;)
    def home():
        cnx = db_connect()
        cur = cnx.cursor()
        output = []
    
        page = request.args.get(&#39;page&#39;, 1)
    
        try:
            page = int(page)
            skip = (page-1)*4
        except:
            abort(404)
       
        stmt_select = &quot;select * from posts limit %s, 4;&quot;
        values=[skip]
    
        cur.execute(stmt_select,values)
        x=cur.fetchall()
    
        for row in reversed(x):
            data = {
               &quot;uid&quot;:row[0],
               &quot;pid&quot;:row[1],
               &quot;subject&quot;:row[2],
               &quot;post_content&quot;:row[3],
               &quot;date&quot;:datetime.fromtimestamp(row[4]),
            }
            output.append(data)
        
        next = page + 1
        previous = page-1
        if previous&lt;1:
        previous=1
        return render_template(&quot;home.html&quot;, persons=output, next=next, previous=previous)

Please explain why it takes two parameters, and then what its use is.


In Flask, what is &quot;request.args&quot; and how is it used?

I want to support pagination in my RESTful API.

My API method should return a JSON list of product via `/products/index`. However, there are potentially thousands of products, and I want to page through them, so my request should look something like this:

    /products/index?page_number=5&amp;page_size=20

But what does my JSON response need to look like? Would API consumers typically expect pagination meta data in the response? Or is only an array of products necessary? Why?

It looks like Twitter&#39;s API includes meta data: https://dev.twitter.com/docs/api/1/get/lists/members (see Example Request).

With meta data:

    {
      &quot;page_number&quot;: 5,
      &quot;page_size&quot;: 20,
      &quot;total_record_count&quot;: 521,
      &quot;records&quot;: [
        {
          &quot;id&quot;: 1,
          &quot;name&quot;: &quot;Widget #1&quot;
        },
        {
          &quot;id&quot;: 2,
          &quot;name&quot;: &quot;Widget #2&quot;
        },
        {
          &quot;id&quot;: 3,
          &quot;name&quot;: &quot;Widget #3&quot;
        }
      ]
    }

Just an array of products (no meta data):

    [
      {
        &quot;id&quot;: 1,
        &quot;name&quot;: &quot;Widget #1&quot;
      },
      {
        &quot;id&quot;: 2,
        &quot;name&quot;: &quot;Widget #2&quot;
      },
      {
        &quot;id&quot;: 3,
        &quot;name&quot;: &quot;Widget #3&quot;
      }
    ]

Pagination response payload from a RESTful API

I have an array and I want to divide them into page according to preset page size.

This is how I do:
     
    private int CalcPagesCount()
    {
        int  totalPage = imagesFound.Length / PageSize;
    
        // add the last page, ugly
        if (imagesFound.Length % PageSize != 0) totalPage++;
        return totalPage;
    }

I feel the calculation is not the simplest (I am poor in math), can you give one simpler calculation formula?



The simplest formula to calculate page count?

I have rows of data coming from database, I would like to have a table with a simple pagination, what is the easiest way of doing it?  
I&#39;d be glad if anyone could provide.

Simple PHP Pagination script

I have 2 components. Both have mat-table and paginators and pagination is working for one component and not working for the other component though the code is similar. Below is my html:

```html
&lt;div class=&quot;mat-elevation-z8&quot;&gt;
    &lt;mat-table [dataSource]=&quot;dataSource&quot; matSort&gt;
        &lt;ng-container matColumnDef=&quot;col1&quot;&gt;
            &lt;mat-header-cell *matHeaderCellDef mat-sort-header&gt; Column1 &lt;/mat-header-cell&gt;
            &lt;mat-cell *matCellDef=&quot;let row&quot;&gt; {{row.col1}} &lt;/mat-cell&gt;
        &lt;/ng-container&gt;

        &lt;ng-container matColumnDef=&quot;col2&quot;&gt;
            &lt;mat-header-cell *matHeaderCellDef mat-sort-header&gt; Column2 &lt;/mat-header-cell&gt;
            &lt;mat-cell *matCellDef=&quot;let row&quot;&gt; {{row.col2}} &lt;/mat-cell&gt;
        &lt;/ng-container&gt;

        &lt;!-- Different columns goes here --&gt;

        &lt;mat-header-row *matHeaderRowDef=&quot;displayedColumns&quot;&gt;&lt;/mat-header-row&gt;
        &lt;mat-row *matRowDef=&quot;let row; columns: displayedColumns;&quot;&gt;&lt;/mat-row&gt;
    &lt;/mat-table&gt;

    &lt;mat-paginator #scheduledOrdersPaginator [pageSizeOptions]=&quot;[5, 10, 20]&quot;&gt;&lt;/mat-paginator&gt;
&lt;/div&gt;
```
And below is my code in component.ts:
```typescript
dataSource: MatTableDataSource&lt;any&gt;;
displayedColumns = [&#39;col1&#39;, &#39;col2&#39;, ... ];

@ViewChild(&#39;scheduledOrdersPaginator&#39;) paginator: MatPaginator;
@ViewChild(MatSort) sort: MatSort;

ngOnInit(): void {
    // Load data
    this.dataSource = new MatTableDataSource(somearray);
    this.dataSource.paginator = this.paginator;
    this.dataSource.sort = this.sort;
}
```
Similar code is working for the other component and table is getting rendered with the pagination properly, no clue what&#39;s wrong with this code.

Any help would be really appreciated

Angular MatPaginator doesn`t get initialized

I am having problems using pagination in [Django][1].  Take the URL below as an example:

    http://127.0.0.1:8000/users/?sort=first_name

On this page I sort a list of users by their first_name.  Without a sort GET variable it defaults to sort by id.  

Now if I click the next link I expect the following URL:

    http://127.0.0.1:8000/users/?sort=first_name&amp;page=2


Instead I lose all get variables and end up with 

    http://127.0.0.1:8000/users/?page=2

This is a problem because the second page is sorted by id instead of first_name.


If I use request.get_full_path I will eventually end up with an ugly URL:

    http://127.0.0.1:8000/users/?sort=first_name&amp;page=2&amp;page=3&amp;page=4

What is the solution?  Is there a way to access the GET variables on the template and replace the value for the page?


I am using pagination as described in [Django&#39;s documentation][2] and my preference is to keep using it.  The template code I am using is similar to this:

    {% if contacts.has_next %}
        &lt;a href=&quot;?page={{ contacts.next_page_number }}&quot;&gt;next&lt;/a&gt;
    {% endif %}

  [1]: http://en.wikipedia.org/wiki/Django_%28web_framework%29
  [2]: http://docs.djangoproject.com/en/dev/topics/pagination/


How to paginate Django with other get variables?

I am trying to convert list to page in spring. I have converted it using 

&gt; new PageImpl&lt;User&gt;(users, pageable, users.size());

But now I having problem with sorting and pagination itself. When I try passing size and page, the pagination doesn&#39;t work.

Here&#39;s the code I am using.

My Controller

    	public ResponseEntity&lt;User&gt; getUsersByProgramId(
			@RequestParam(name = &quot;programId&quot;, required = true) Integer programId Pageable pageable) {

		List&lt;User&gt; users = userService.findAllByProgramId(programId);
		Page&lt;User&gt; pages = new PageImpl&lt;User&gt;(users, pageable, users.size());

		return new ResponseEntity&lt;&gt;(pages, HttpStatus.OK);
	}


Here is my user Repo

    public interface UserRepo extends JpaRepository&lt;User, Integer&gt;{

	public List&lt;User&gt; findAllByProgramId(Integer programId);

Here is my service

    	public List&lt;User&gt; findAllByProgramId(Integer programId);


Conversion of List to Page in Spring

I was wondering if someone could explain how to use [will_paginate][1] on an array of objects?

For example, on my site I have an opinion section where users can rate the opinions. Here&#39;s a method I wrote to gather the users who have rated the opinion:

    def agree_list
      list = OpinionRating.find_all_by_opinion_id(params[:id])
      @agree_list = []
      list.each do |r|
        user = Profile.find(r.profile_id)
        @agree_list &lt;&lt; user
      end
    end

Thank you


  [1]: https://github.com/mislav/will_paginate

Ruby on Rails will_paginate an array

I have success working tableview with json parsing codes.But may have 1000 more item so need pagination when scrolling bottom side. I dont know how can i do this my codes under below. For objective-c have a lot of example but for swift i didnt find working example. Im waiting your helps. I think will be help too many people. Thank you ! 

    import UIKit
    
    class ViewController: UIViewController, UITableViewDataSource,UITableViewDelegate {
        
        let kSuccessTitle = &quot;Congratulations&quot;
        let kErrorTitle = &quot;Connection error&quot;
        let kNoticeTitle = &quot;Notice&quot;
        let kWarningTitle = &quot;Warning&quot;
        let kInfoTitle = &quot;Info&quot;
        let kSubtitle = &quot;You&#39;ve just displayed this awesome Pop Up View&quot;
        
        
        @IBOutlet weak var myTableView: UITableView!
        @IBOutlet weak var myActivityIndicator: UIActivityIndicatorView!
        
        var privateList = [String]()
        
        override func viewDidLoad() {
            super.viewDidLoad()
            // Do any additional setup after loading the view, typically from a nib.
            
        }
        
        override func viewWillAppear(animated: Bool) {
            super.viewWillAppear(animated)
            
            loadItems()
            
        }
        
        override func didReceiveMemoryWarning() {
            super.didReceiveMemoryWarning()
            // Dispose of any resources that can be recreated.
        }
        
        
        internal func tableView(tableView: UITableView, numberOfRowsInSection section: Int) -&gt; Int
        {
            return privateList.count
        }
        
        
        
        
        internal func tableView(tableView: UITableView, cellForRowAtIndexPath indexPath: NSIndexPath) -&gt; UITableViewCell
        {
            
           let cell:myCell = tableView.dequeueReusableCellWithIdentifier(&quot;myCell&quot;) as! myCell
            
            cell.titleLabel.text = privateList[indexPath.row]
            
            
            return cell
        }
        
        
        func tableView(tableView: UITableView, commitEditingStyle editingStyle: UITableViewCellEditingStyle, forRowAtIndexPath indexPath: NSIndexPath) {
        
            if (editingStyle == UITableViewCellEditingStyle.Delete){
               
             print(indexPath.row)
             
                
                let alert = SCLAlertView()
                alert.addButton(&quot;Hayır&quot;){ }
                alert.addButton(&quot;Evet&quot;) {
                
                    self.myTableView.beginUpdates()
                    
                     self.privateList.removeAtIndex(indexPath.row)
                    tableView.deleteRowsAtIndexPaths([indexPath], withRowAnimation: UITableViewRowAnimation.Left)
                    print(&quot;Silindi&quot;)
                    
                    self.myTableView.endUpdates()
                    
                      self.loadItems()
                    
                }
                alert.showSuccess(kSuccessTitle, subTitle: kSubtitle)
                
            }
            
            
        }
        
        
        
       
        
        func tableView(tableView: UITableView, canEditRowAtIndexPath indexPath: NSIndexPath) -&gt; Bool {
            // the cells you would like the actions to appear needs to be editable
            return true
        }
        
        
        
        override func prepareForSegue(segue: UIStoryboardSegue, sender: AnyObject?) {
           
            
            if(segue.identifier == &quot;Detail&quot;) {
                
                let destinationView = segue.destinationViewController as! DetailViewController
                
                if let indexPath = myTableView.indexPathForCell(sender as! UITableViewCell) {
                   
                    destinationView.privateLista = privateList[indexPath.row]
                    
                }
            }
        }
        
        
        
        internal func tableView(tableView: UITableView, estimatedHeightForHeaderInSection section: Int) -&gt; CGFloat
        {
            return 0.0
        }
        
        
        func loadItems()
        {
         loadItemsNow(&quot;privateList&quot;)
          
        }
        
        func loadItemsNow(listType:String){
            myActivityIndicator.startAnimating()
            let listUrlString =  &quot;http://bla.com/json2.php?listType=&quot; + listType + &quot;&amp;t=&quot; + NSUUID().UUIDString
            let myUrl = NSURL(string: listUrlString);
            let request = NSMutableURLRequest(URL:myUrl!);
            request.HTTPMethod = &quot;GET&quot;;
            
            let task = NSURLSession.sharedSession().dataTaskWithRequest(request) {
                data, response, error in
                
                if error != nil {
                    print(error!.localizedDescription)
                    dispatch_async(dispatch_get_main_queue(),{
                        self.myActivityIndicator.stopAnimating()
                    })
                    
                    return
                }
                
                
                do {
                    
                    let json = try NSJSONSerialization.JSONObjectWithData(data!, options: .MutableContainers) as? NSArray
                    
                    if let parseJSON = json {
                        
                      
                            self.privateList = parseJSON as! [String]
                       
                    }
                    
                } catch {
                    print(error)
                    
                }
                
                dispatch_async(dispatch_get_main_queue(),{
                    self.myActivityIndicator.stopAnimating()
                    self.myTableView.reloadData()
                })
                
                
            }
            
            task.resume()
        }
        
        
    }



Swift tableView Pagination

It&#39;s said that using skip() for pagination in MongoDB collection with many records is slow and not recommended.

Ranged pagination (based on &gt;_id comparsion) could be used 

    db.items.find({_id: {$gt: ObjectId(&#39;4f4a3ba2751e88780b000000&#39;)}});

It&#39;s good for displaying prev. &amp; next buttons - but it&#39;s not very easy to implement when you want to display actual page numbers 1 ... 5 6 7 ... 124 - you need to pre-calculate from which &quot;_id&quot; each page starts.

So I have two questions:

1) When should I start worry about that? When there&#39;re &quot;too many records&quot; with noticeable slowdown for skip()? 1 000? 1 000 000?

2) What is the best approach to show links with actual page numbers when using ranged pagination?

MongoDB ranged pagination

I am interested in optimizing a &quot;pagination&quot; solution I&#39;m working on with MongoDB. My problem is straight forward. I usually limit the number of documents returned using the `limit()` functionality. This forces me to issue a redundant query without the `limit()` function in order for me to also capture the total number of documents in the query so I can pass to that to the client letting them know they&#39;ll have to issue an additional request(s) to retrieve the rest of the documents.

Is there a way to condense this into 1 query? Get the total number of documents but at the same time only retrieve a subset using `limit()`? Is there a different way to think about this problem than I am approaching it?

Get a count of total documents with MongoDB when using limit

**Laravel 4.2** has the option to specify a custom view in `app/config/view.php` such as:

    /*
    |--------------------------------------------------------------------------
    | Pagination View
    |--------------------------------------------------------------------------
    |
    | This view will be used to render the pagination link output, and can
    | be easily customized here to show any view you like. A clean view
    | compatible with Twitter&#39;s Bootstrap is given to you by default.
    |
    */
    &#39;pagination&#39; =&gt; &#39;pagination_slider-alt&#39;

This is gone in **Laravel 5** at least regarding `view.php`.

Is there a way to replicate this behavior in **Laravel 5**?

Custom pagination view in Laravel 5

I am new to ReactJS and am creating a simple TODO application in it. Actually, it is a very basic app with no DB connection, tasks are stored in an array. I added Edit and Delete functionality to it now I want to add pagination. 

How do I implement it? Any help will be appreciated. Thank you...!!

How to implement pagination in React

this seems like very simple maths but somehow, my brain cant think ... 

i am trying to implement pagination and will need to calculate the item offset to use in limiting my result set. i am having problems calculating what index the first item of the page should have. 

eg. 

    with 1 page having 10 items
    
    page 1 will have items 1 - 10
    page 2 ............... 11 - 20
    page 3 ............... 21 - 30

i thought of

    offset = page * itemsPerPage + 1

but this will not be the case for page 1. there must be a formula for this? am using PHP/Zend_Paginator/Doctrine2 but this should be language independent 

*wonder if this should be in the the maths stack exchange site* 

Calculating item offset for pagination

I&#39;m trying to do the pagination, but there is an error:

&gt;[Syntax Error] line 0, col 57: Error: Expected end of string, got &#39;limit&#39;

I&#39;m not quite sure if this is the right syntax (and logic) to make my query:

&lt;!-- language: php --&gt;

    public function getFriendsFromTo ($user, $limit, $offset)
    {
         return $this-&gt;getEntityManager()
            -&gt;createQuery(&#39;SELECT f FROM EMMyFriendsBundle:Friend f WHERE f.user=&#39;.$user.&#39; limit &#39;.$limit. &#39;offset&#39; .$offset)
            -&gt;getResult();
    }

Friends and users are related manyToOne and oneToMany, so in the friends table there is a field - user_id.

This is in my controller:

&lt;!-- language: php --&gt;

    $user = $this-&gt;get(&#39;security.context&#39;)-&gt;getToken()-&gt;getUser();
    $id = $user-&gt;getId();
    
    $friends = $user-&gt;getFriends();
    $result = count($friends)
    $FR_PER_PAGE = 7;
    $pages = $result/$FR_PER_PAGE;
            
    $em = $this-&gt;getDoctrine()-&gt;getEntityManager();
    $friends = $em-&gt;getRepository(&#39;EMMyFriendsBundle:Friend&#39;)
             -&gt;getFriendsFromTo($id, $FR_PER_PAGE, $page*$FR_PER_PAGE); 

I know that it&#39;s stupid and even wrong (especially the third parameter to be `$page*$FR_PER_PAGE`), but I just wanted to try if the query works, and it didn&#39;t.

Use Limit and Offset in Doctrine2 query

I have a `List` of entities.
How do I convert it to `Page` Object using Spring MVC 4 and Spring Data JPA?

How to convert a list of enity object to page object in Spring MVC (JPA)?

I&#39;m new to angular and trying to implement pagination in my app. I am trying to use [this material component.][1]

With the code below, I can get `length`, `pagesize`, and `pageSizeOptions` in my `.ts` file

&lt;!-- language: lang-xml --&gt;

    &lt;md-paginator [length]=&quot;length&quot;
                  [pageSize]=&quot;pageSize&quot;
                  [pageSizeOptions]=&quot;pageSizeOptions&quot;
    &lt;/md-paginator&gt;

&lt;!-- language: lang-js --&gt;

    export class PaginatorConfigurableExample {
    
      length = 100;
      pageSize = 10;
      pageSizeOptions = [5, 10, 25, 100];
    
      }
    }


but I can&#39;t seem to trigger a function to change the data on the table above when the page is changed. Also, how do I use the `nextPage`, `previousPage`, `hasNextPage`, and `hasPreviousPage` methods?

[1]: https://material.angular.io/components/paginator/overview

How to use paginator from material angular?

I want the user to be able to specify the limit (the size of the amount returned) and offset (the first record returned / index returned) in my query method. 
 
Here are my classes without any paging capabilities.
My entity:

    @Entity
    public Employee {
        @Id
        @GeneratedValue(strategy=GenerationType.AUTO)
        private int id;
    
        @Column(name=&quot;NAME&quot;)
        private String name;
    
        //getters and setters
    }


My repository:

    public interface EmployeeRepository extends JpaRepository&lt;Employee, Integer&gt; {
        
        @Query(&quot;SELECT e FROM Employee e WHERE e.name LIKE :name ORDER BY e.id&quot;)
        public List&lt;Employee&gt; findByName(@Param(&quot;name&quot;) String name);
    }

My service interface:

    public interface EmployeeService {
    
        public List&lt;Employee&gt; findByName(String name);
    }

My service implementation:

    public class EmployeeServiceImpl {
    
        @Resource
        EmployeeRepository repository;
    
        @Override
        public List&lt;Employee&gt; findByName(String name) {
            return repository.findByName(name);
        }
    }


Now here is my attempt at providing paging capabilities that support offset and limit.
My entity class remains the same.

My &quot;new&quot; repository takes in a pageable parameter:

    public interface EmployeeRepository extends JpaRepository&lt;Employee, Integer&gt; {
    
        @Query(&quot;SELECT e FROM Employee e WHERE e.name LIKE :name ORDER BY e.id&quot;)
        public List&lt;Employee&gt; findByName(@Param(&quot;name&quot;) String name, Pageable pageable);
    }

My &quot;new&quot; service interface takes in two additional parameters:

    public interface EmployeeService {
        
        public List&lt;Employee&gt; findByName(String name, int offset, int limit);
    }

My &quot;new&quot; service implementation:

    public class EmployeeServiceImpl {
        
        @Resource
        EmployeeRepository repository;
        
        @Override
        public List&lt;Employee&gt; findByName(String name, int offset, int limit) {
            return repository.findByName(name, new PageRequest(offset, limit);
        }
    }

This however isn&#39;t what i want.  PageRequest specifies the page and size (page # and the size of the page).  Now specifying the size is exactly what I want, however, I don&#39;t want to specify the starting page #, I want the user to be able to specify the starting record / index.  I want something similar to

    public List&lt;Employee&gt; findByName(String name, int offset, int limit) {
        TypedQuery&lt;Employee&gt; query = entityManager.createQuery(&quot;SELECT e FROM Employee e WHERE e.name LIKE :name ORDER BY e.id&quot;, Employee.class);
        query.setFirstResult(offset);
        query.setMaxResults(limit);
        return query.getResultList();
    }

Specifically the setFirstResult() and setMaxResult() methods.  But I can&#39;t use this method because I want to use the Employee repository interface.  (Or is it actually better to define queries through the entityManager?)  Anyways, is there a way to specify the offset without using the entityManager?  Thanks in advance! 

Pagination in Spring Data JPA (limit and offset)

I am implementing datatbales and according to my requirement, most of the things have been resolved except the pagination issue. In my case for every time pagination navigation is displaying. I want to disable the pagination navigation if there is only one page at all.How to do that? My code is like:

**JS**

    &lt;script&gt;
      function fnFilterColumn(i) {

        $(&#39;#example&#39;).dataTable().fnFilter(
          $(&quot;#col&quot; + (i + 1) + &quot;_filter&quot;).val(),
          i
        );
      }
      $(document).ready(function() {


        $(&#39;#example&#39;).dataTable({
          &quot;bProcessing&quot;: true,
          &quot;sAjaxSource&quot;: &quot;datatable-interestdb.php&quot;,
          &quot;bJQueryUI&quot;: true,
          &quot;sPaginationType&quot;: &quot;full_numbers&quot;,
          &quot;sDom&quot;: &#39;T&lt;&quot;clear&quot;&gt;lfrtip&#39;,
          &quot;oTableTools&quot;: {
            &quot;aButtons&quot;: [

              {
                &quot;sExtends&quot;: &quot;csv&quot;,
                &quot;sButtonText&quot;: &quot;Save to CSV&quot;
              }
            ]
          },
          &quot;oLanguage&quot;: {
            &quot;sSearch&quot;: &quot;Search all columns:&quot;
          }


        });


        $(&quot;#example&quot;).dataTable().columnFilter({
          aoColumns: [
            null,
            null,
            null,
            null
          ]
        });


        $(&quot;#col1_filter&quot;).keyup(function() {
          fnFilterColumn(0);
        });

      });
    &lt;/script&gt;

**HTML**

    &lt;table cellpadding=&quot;3&quot; cellspacing=&quot;0&quot; border=&quot;0&quot; class=&quot;display userTable&quot; aria-describedby=&quot;example_info&quot;&gt;

      &lt;tbody&gt;
        &lt;tr id=&quot;filter_col1&quot;&gt;
          &lt;td&gt;Interest:&lt;/td&gt;
          &lt;td&gt;
            &lt;input type=&quot;text&quot; name=&quot;col1_filter&quot; id=&quot;col1_filter&quot;&gt;
          &lt;/td&gt;
        &lt;/tr&gt;
      &lt;/tbody&gt;
    &lt;/table&gt;


    &lt;table width=&quot;100%&quot; border=&quot;0&quot; align=&quot;center&quot; cellpadding=&quot;2&quot; cellspacing=&quot;1&quot; class=&quot;form_table display&quot; id=&quot;example&quot;&gt;

      &lt;thead&gt;
        &lt;tr&gt;
          &lt;th class=&quot;sorting_asc&quot; width=&quot;25%&quot;&gt;Interest&lt;/th&gt;
          &lt;th width=&quot;25%&quot;&gt;Name&lt;/th&gt;
          &lt;th width=&quot;25%&quot;&gt;Email&lt;/th&gt;
          &lt;th width=&quot;25%&quot;&gt;Contact No&lt;/th&gt;
        &lt;/tr&gt;
      &lt;/thead&gt;
      &lt;tbody&gt;

        &lt;tr&gt;
          &lt;td colspan=&quot;4&quot; class=&quot;dataTables_empty&quot;&gt;Loading data from server&lt;/td&gt;
        &lt;/tr&gt;
      &lt;/tbody&gt;
      &lt;tfoot&gt;
        &lt;tr&gt;
          &lt;th&gt;&lt;/th&gt;
          &lt;th&gt;&lt;/th&gt;
          &lt;th&gt;&lt;/th&gt;
          &lt;th&gt;&lt;/th&gt;
        &lt;/tr&gt;
      &lt;/tfoot&gt;


    &lt;/table&gt;

disable pagination if there is only one page in datatables

How can I split the content of a HTML file in screen-sized chunks to &quot;paginate&quot; it in a WebKit browser? 

Each &quot;page&quot; should show a complete amount of text. This means that a line of text must not be cut in half in the top or bottom border of the screen.

**Edit**

This question was originally tagged &quot;Android&quot; as my intent is to build an Android ePub reader. However, it appears that the solution can be implemented just with JavaScript and CSS so I broadened the scope of the question to make it platform-independent.


HTML book-like pagination

This is similar to to [this question][1] which doesn&#39;t have any answers. I&#39;ve read all about how to use cursors with the [twitter][2], [facebook][3], and [disqus][4] api&#39;s and also [this article][5] about how disqus generally built their cursors, but I still cannot seem to grok the concept of how they work and how to implement a similar solution in my own projects. Can someone explain specifically the different techniques and concepts behind them?


  [1]: https://stackoverflow.com/questions/17234203/building-a-pagination-cursor
  [2]: https://dev.twitter.com/docs/misc/cursoring
  [3]: https://developers.facebook.com/docs/reference/api/pagination/
  [4]: http://disqus.com/api/docs/cursors/
  [5]: https://cra.mr/2011/03/08/building-cursors-for-the-disqus-api

How to implement cursors for pagination in an api

Is there any out-of-the-box, easy to implement, standard pagination component/tag-lib or code-sample available for pagination in Spring MVC?

How to implement pagination in Spring MVC 3

How do you do pagination in SQL Server 2008 ?

How to do pagination in SQL Server 2008

I&#39;m doing a pagination feature using Codeigniter but I think this applies to PHP/mySQL coding in general.

I am retrieving directory listings using offset and limit depending on how many results I want per page. However to know the total number of pages required, I need to know (total number of results)/(limit). Right now I am thinking of running the SQL query a second time then count the number of rows required but without using LIMIT. But I think this seems to be a waste of computational resources. 

Are there any better ways? Thanks!

EDIT: My SQL query uses WHERE as well to select all rows with a particular &#39;category_id&#39;

Find total number of results in mySQL query with offset+limit

What is it best to handle pagination? Server side or doing it dynamically using javascript?

I&#39;m working on a project which is heavy on the ajax and pulling in data dynamically, so I&#39;ve been working on a javascript pagination system that uses the dom - but I&#39;m starting to think it would be better to handle it all server side.

What are everyone&#39;s thoughts?

Pagination: Server Side or Client Side?

I have a Table (multiple rows, multiple columns, see below ) that is longer than one page. 
How can I tell LaTeX to continue on the next page. 

 - Adding a \newpage didn&#39;t work
 - Manually &#39;ending&#39; and &#39;reopening&#39; the table works, but is very tedious, since the table will be many pages long.

        \begin{tabular}{lp{13cm}} 
            AAAAAAAAAA  &amp; FOOBAR FOOBAR FOOBAR FOOBAR FOOBAR\\
            BBBBBBBBBB  &amp; FOOBAR FOOBAR FOOBAR FOOBAR FOOBAR\\
            CCCCCCCCCC  &amp; FOOBAR FOOBAR FOOBAR FOOBAR FOOBAR\\
          
            ...
    
            ZZZZZZZZZ  &amp;  FOOBAR FOOBAR FOOBAR FOOBAR FOOBAR\\
         \end{tabular}



How to stretch a table over multiple pages

With [DataTable][1] I can order, list, do pagination but I want to detect when the pagination changes, I&#39;ve seen the [API][2] but the only one I can do is change the page but no detect this change.

  [1]: http://datatables.net/
  [2]: http://datatables.net/api

All Pagination Solutions on Gang of Coders

Total of 48 Pagination Solutions