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-666) Define Deep Update and Deep Upsert operations

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

Michael Pizzo commented on ODATA-666:

Needs to be aligned with ODATA-876.

In both cases we are defining a nested representation of a change; in the case of ODATA-876 it is a change reported from the service and in the case of ODATA-666 it is the representation of the change the client would like to submit to the service.  The payload and semantics should be the same; I should be able to take a delta response and use it to submit those same changes to a different service.  However, currently the semantics differ.

In the case of ODATA-666, a nested collection represents the full membership of that collection (according to any applied filter in the expand).  Removed entities are no longer related.  In this proposal, the nested collection represents the subset of items to be changed. Entities omitted from the nested collection are unchanged.

> 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

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