[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=61281#comment-61281 ] Steven Legg commented on ODATA-666: ----------------------------------- Is the proposed text for section 11.4.3.1 saying that the request must include all the existing related entities (for a contained navigation property) even if they aren't being updated ? If any such entity is omitted is that an error ? I could read the text as implying that a related entity that is omitted is no longer a member of the collection, contrary to the apparent intent. > 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]