Clarify, in OData Protocol, that $skip and $top are not allowed to be appended to a next link

    • Type: Bug
    • Resolution: Fixed
    • Priority: Minor
    • V4.0_WD01
    • Affects Version/s: V4.0_WD01
    • Component/s: Protocol
    • None
    • Environment:

      [Proposed]

    • Hide

      Clarify that $skip and $top, as well as $select, $expand, $filter, $orderby may not be applied to a next link returned by the service. The next link encodes all of these values from the initial request. In terms of execution order, all of these operations would be evaluated as part of the next link.

      If $skiptoken is used within the next link (an implementation detail), it should be evaluated after $skip and $top.

      Show
      Clarify that $skip and $top, as well as $select, $expand, $filter, $orderby may not be applied to a next link returned by the service. The next link encodes all of these values from the initial request. In terms of execution order, all of these operations would be evaluated as part of the next link. If $skiptoken is used within the next link (an implementation detail), it should be evaluated after $skip and $top.
    • Show
      https://www.oasis-open.org/apps/org/workgroup/odata/download.php/47541/odata-core-v1.0-wd01-part1-protocol-2012-11-22.doc Accepted: https://www.oasis-open.org/apps/org/workgroup/odata/download.php/47595/latest/odata-meeting-16_on-20121129-minutes.html

      As discussed in 2012-11-08 face to face meeting, it does not seem useful, and in fact seems a bad idea, for the client to attempt to apply $skip and $top to a next link.

            Assignee:
            handl
            Reporter:
            Michael Pizzo (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: