[OASIS Issue Tracker] (ODATA-666) Define Deep Update and Deep Upsert operations

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

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

Ralf Handl updated ODATA-666:
-----------------------------

    Labels: AdoptionBlocker Usability  (was: AdoptionBlocker Gap Usability)

> 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
>            Reporter: Ralf Handl
>              Labels: AdoptionBlocker, Usability
>             Fix For: V4.1_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)