[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (ODATA-1057) Consider PATCH to /$delta for delta update rather than rely on context url
[ https://issues.oasis-open.org/browse/ODATA-1057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralf Handl updated ODATA-1057: ------------------------------ Fix Version/s: V4.01_CSD02 (was: V4.01_CS02) Affects Version/s: V4.01_CSD01 (was: V4.01_CS01) What would GET to collection/$delta return? I'd rather not invent a new resource type. > Consider PATCH to /$delta for delta update rather than rely on context url > -------------------------------------------------------------------------- > > Key: ODATA-1057 > URL: https://issues.oasis-open.org/browse/ODATA-1057 > Project: OASIS Open Data Protocol (OData) TC > Issue Type: Bug > Components: Protocol > Affects Versions: V4.01_CSD01 > Environment: [Proposed] > Reporter: Michael Pizzo > Fix For: V4.01_CSD02 > > > As of 4.01 we support PATCH to a collection of entities. The PATCH is either interpreted as a set operation (if the payload is a single entity) or applied as a delta payload (if the payload has a context URL of #$delta. > Rather than distinguishing on payload, what if we said that PATCH to a collection of entities is always interpreted as a set operation (same as PATCH to a collection of complex or primitive types) and to apply a delta to a collection of entities you would PATCH to the resource with /$delta appended. -- 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]