Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Great question.</p> <p>$inlinecount out of the box only works when you're sending back OData responses. The reason for this is that OData defines special fields in the data that XML and JSON don't define. So in OData a response might look like this:</p> <pre><code>{ "odata.metadata":"http://localhost:12345/odata/$metadata#Customers", "odata.count":"4", "value":[ ... ] } </code></pre> <p>Notice the wrapper with the "odata.count" property. This is different from the way the default XML and JSON formatters write out data because they don't have wrappers for this additional information. So other formatters are by default unchanged.</p> <p>Now you have several options:</p> <p>You could choose to use the OData format. For this, you'll want to follow the instructions in this blog post:</p> <p><a href="http://blogs.msdn.com/b/webdev/archive/2013/01/29/getting-started-with-asp-net-webapi-odata-in-3-simple-steps.aspx">http://blogs.msdn.com/b/webdev/archive/2013/01/29/getting-started-with-asp-net-webapi-odata-in-3-simple-steps.aspx</a></p> <p>You could also choose to instead return a <code>PageResult&lt;T&gt;</code>. This looks like this:</p> <pre><code>public PageResult&lt;Customer&gt; Get(ODataQueryOptions&lt;Customer&gt; queryOptions) { IQueryable results = queryOptions.ApplyTo(_customers.AsQueryable()); return new PageResult&lt;Customer&gt;(results as IEnumerable&lt;Customer&gt;, Request.GetNextPageLink(), Request.GetInlineCount()); } </code></pre> <p>This should work fine for OData, JSON, and XML by adding a wrapper object for XML and JSON that can include the Count and the next page link.</p>
    singulars
    1. This table or related slice is empty.
    1. POWeb API OData Inlinecount not working
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USYoussef Moussaoui
    1. USYoussef Moussaoui
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POWeb API OData Inlinecount not working
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COFrom reading the MS docs on this http://www.asp.net/web-api/overview/odata-support-in-aspnet-web-api/supporting-odata-query-options, it sounds like it should work out of the box, like filtering and sorting?
      singulars
      1. PO
      1. UStom
    2. COThe doc is wrong in this case. The difference is that filtering doesn't need to change the "shape" of the data, but adding an inline count and a next page link do. So filtering works out of the box for other formatters, but $inlinecount doesn't.
      singulars
      1. PO
      1. USYoussef Moussaoui
    3. COTake a look at breezejs.com. The latest version works with all of the MS OData syntax and all supports inlinecount, select and expand.
      singulars
      1. PO
      1. USJay Traband
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload