Ensure paging settings are followed

Paging can be done in YQL using LIMIT and OFFSET in the query. Integrate this with pager handler in views.

The total item can be retrieved by submitting YQL query with no LIMIT/OFFSET specified which might not be the preferred way of getting the total items.

Will update this issue after I studied the pager plugin.

(copied from YQL Docs)

The default number of items for a remote limit varies with the table. For most tables, the default number of items is 10.
The maximum number of items also varies with table. To get the maximum number of items, enter 0 in parentheses after the table name. The following statement returns 1000 items from the search.web table:
select title from search.web(0) where query="pizza"

The problem is this query is running very slow..

Suggested solution:

YQL Query settings will contain the "base table name" along with the "row limit of the table" (specified manually, later ajax button can be added there to fill in the textbox).

This is due to the design of YQL that the limit is highly varied for each table. For example: local.search (limit = 260), flickr.photos.recent (limit = 5000).

This is committed. This issue is considered fix in a sense that it implements the basic of paging into YQL querying. However, it introduces another issue: #876636: Pager has performance issue