[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (ODATA-873) Define a default order for deep inserted entities in responses
[ https://issues.oasis-open.org/browse/ODATA-873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63050#comment-63050 ] Michael Pizzo commented on ODATA-873: ------------------------------------- from 2016-7-2016: Concern about forcing service to retain ordering. Perhaps use an instance annotation (@odata.contentId?) that is not (necessarily) persisted -- the client specifies and the service echos. > 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)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]