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=61263#comment-61263 ] 

Gerald Krause commented on ODATA-666:

In fact, we have a chain of dependencies from 876 to 666:

876 clarifies inlined related entities in delta responses.

613 defines how to post the output of 876, that is delta responses to entity sets, which may also include entities with inlined contained/related entities.

666 defines deep updates/upserts for a single entity: As a consequence of 876, it would adopt the proposal in 876 for inlined (nested) related/contained entities. This would also imply that the differential update behavior would no longer be in scope of a deep upsert (666) and therefore be exclusively covered by 613.

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