← Prev in month ← Prev in thread

[OASIS Issue Tracker] (ODATA-607) Section 4.5.4: explicitly state that @odata.count can be applied to expanded to-many navigation properties

From
OASIS Issues Tracker <>
Date
2014-04-03T16:25:29+00:00
ID
JIRA.23312.1394443140000.743.1396542330981@customer-jira-611
Thread
[OASIS Issue Tracker] (ODATA-607) Section 4.5.4: explicitly state that @odata.count can be applied to expanded to-many navigation properties
[ https://tools.oasis-open.org/issues/browse/ODATA-607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Pizzo updated ODATA-607:
--------------------------------

    Summary: Section 4.5.4: explicitly state that @odata.count can be applied to expanded to-many navigation properties  (was: Section 4.5.4: explicitly state that @odata.count can be applied to expanded to-many navigation properties with server-driven paging)

> Section 4.5.4: explicitly state that @odata.count can be applied to expanded to-many navigation properties
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: ODATA-607
>                 URL: https://tools.oasis-open.org/issues/browse/ODATA-607
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData JSON Format
>    Affects Versions: V4.0_OS
>            Reporter: Ralf Handl
>            Priority: Minor
>             Fix For: V4.0_ERRATA01
>
>
> We allow $count=true nested after $expand, resulting in @odata.count annotations in the inlined representation of to-many navigation properties. This can be deduced from other specification text but is not explicitly stated in the section on odata.count.



--
This message was sent by Atlassian JIRA
(v6.1.1#6155)
← Prev in month ← Prev in thread