[OASIS Issue Tracker] (ODATA-873) Define a default order for deep inserted entities in responses

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

     [ https://issues.oasis-open.org/browse/ODATA-873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matthew Borges updated ODATA-873:
---------------------------------

    Description: There is no defined order for expanded nested entities in the response to a request (POST, PUT or PATCH) that creates new entities by a deep insert.  (was: There is no defined default order for nested entities in the response to a POST that had a deep insert and a Prefer header with a value of return=representation.

This is somewhat related to ODATA-614 in that ODATA-614 proposes to allow $expand, $select, etc to specify the response shape.)
       Proposal: A response to a request (POST, PUT, or PATCH) that creates nested entities and that specified the Prefer header with a value of return=representation MUST contain the nested entities in the same order they appeared in the request unless explicitly overridden by an $orderby clause.  (was: Nested entities in a response to a POST request with a deep insert and that specified the Prefer header with a value of return=representation MUST be returned in the same order they appeared in the POST request unless overridden by an $orderby clause.)

> Define a default order for deep inserted entities in responses
> --------------------------------------------------------------
>
>                 Key: ODATA-873
>                 URL: https://issues.oasis-open.org/browse/ODATA-873
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData Protocol
>    Affects Versions: V4.0_ERRATA02
>            Reporter: Matthew Borges
>            Priority: Minor
>             Fix For: V4.01_WD01
>
>
> There is no defined order for expanded nested entities in the response to a request (POST, PUT or PATCH) that creates new entities by a deep insert.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)