[ https://issues.oasis-open.org/browse/ODATA-666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61282#comment-61282 ]
Ralf Handl commented on ODATA-666:
----------------------------------
Yes, all still related entities have to be present in a deep update, entities not listed are treated as unrelated/deleted from the collection.
ODATA-613 allows to alternatively use the delta format where related entities aren't nested and instead deleted entities, deleted links, and added links can be sent.
> Define Deep Update and Deep Upsert operations
> ---------------------------------------------
>
> Key: ODATA-666
> URL: https://issues.oasis-open.org/browse/ODATA-666
> Project: OASIS Open Data Protocol (OData) TC
> Issue Type: Improvement
> Components: Implementing OData, OData ATOM Format, OData JSON Format, OData Protocol
> Affects Versions: V4.0_OS
> Environment: Set Operations; [Proposed]
> Reporter: Ralf Handl
> Assignee: Ralf Handl
> Labels: AdoptionBlocker, Usability
> Fix For: V4.01_WD01
>
>
> Similar to Deep Insert allow including nested entities that may already exist, in which case they are updated.
> Also allow nested "tombstones" to remove entities.
> Allow entity references to just create relations as an alternative to odata.bind (in the long run: retire odata.bind and use references everywhere).
> Use odata.etag annotation for conditional update of nested entities.
--
This message was sent by Atlassian JIRA
(v6.2.2#6258)
