[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=61274#comment-61274 ] Ralf Handl commented on ODATA-666: ---------------------------------- PATCH: is it allowed to provide only a subset of the properties of related entities, and will then only those properties be updated? What if the service cannot insert a new related entity from the provided subset of properties? Should we restrict deep update to PUT to evade these questions? > 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)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]