OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

odata message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] (ODATA-924) Define semantics for PUT against a single entity with nested content


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

Michael Pizzo updated ODATA-924:
--------------------------------

    Proposal: 
Define that, when you do a PUT,
1) You can include new entities, existing entities, and references to existing entities
2) Existing entities are updated using PUT semantics
a) entities to be updated must have either @odata.id or key fields, otherwise interpreted as an insert
3) The end result of the PUT is that the specified entities and entity references are the full set of entities related according to that relationship.

  was:
Define that, when you do a PUT,
1) You can include new entities and references to existing entities, but not content for existing entities
2) The end result of the PUT is that the existing (references) and new (entities) are the full set of entities related according to that relationship.


> Define semantics for PUT against a single entity with nested content
> --------------------------------------------------------------------
>
>                 Key: ODATA-924
>                 URL: https://issues.oasis-open.org/browse/ODATA-924
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: OData Protocol
>    Affects Versions: V4.0_ERRATA03
>         Environment: [Proposed]
>            Reporter: Michael Pizzo
>             Fix For: V4.01_WD01
>
>
> In ODATA-666 we defined semantics for a PATCH request to a single entity or collection of entities that contained nested entities.
> We said it didn't make sense to do a PUT against a collection of entities, but need to define the semantics (if allowed) of a PUT operation against a single entity where the payload contains nested entities.



--
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]