OData pagination with WebApi ( $inlinecount )

前端 未结 3 1962
情话喂你
情话喂你 2021-01-02 06:58

I am using OData to paginate a long list of items returned from a web api call. I can filter the data via the url with the start and end index.

The question I have i

相关标签:
3条回答
  • 2021-01-02 07:09

    Try this approach: http://www.strathweb.com/2012/08/supporting-odata-inlinecount-with-the-new-web-api-odata-preview-package/

    It uses the latest Web API OData package.

    Until the finalized Web API OData package is shipped (sometime this fall, should be around in November), when the $inlinecount is supported out of the box, this solution is likely the best bet.

    0 讨论(0)
  • 2021-01-02 07:11

    You can use $inlinecount=allpages in the query to get the count of all the entities in the results without the top and skip. For example:

    http://services.odata.org/OData/OData.svc/Products?$top=1&skip=1&$inlinecount=allpages

    Returns a single product but also inline count of 9 (since there are 9 products in the entity set).

    0 讨论(0)
  • 2021-01-02 07:21

    I had the exact issue last week. Check out Extending your ASP.NET Web API responses with useful metadata

    I used this post and sample code to get a paging grid up and running using OData. As detailed in the sample I created a delegating handler to capture the HttpResponseMessage and wrap it in custom metadata that includes an item count. A custom attribute, CustomQueryableAttribute, is also created that inherits the default QueryableAttribute.

    It may sound a little complex here but is actually pretty simple to implement. I had something up and running in about 30 minutes.

    Hopefully future versions of the Web API have more complete OData support.

    EDIT: Odata support will NOT be shipping with the Web API. The queryable attribute is being removed for the RTM release. More complete OData support will be available sometime after the initial relase via a separate Nuget package.

    0 讨论(0)
提交回复
热议问题