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-1302) Support PUT to replace a collection of entities


Michael Pizzo created ODATA-1302:
------------------------------------

             Summary: Support PUT to replace a collection of entities
                 Key: ODATA-1302
                 URL: https://issues.oasis-open.org/browse/ODATA-1302
             Project: OASIS Open Data Protocol (OData) TC
          Issue Type: Bug
          Components: Protocol
    Affects Versions: V4.01_CSD03
         Environment: Proposed
            Reporter: Michael Pizzo
             Fix For: V4.0_CSD04


In 4.01 we added support for doing a deep update by doing a PUT against an entity with an inline set of objects; the semantics are that, at the end of the operation, the entity contains exactly the entities specified in the payload; any entities not specified are removed (and, for containment or if an integrity constraint exists, deleted). This is the same semantics as doing a PUT with a nested collection of primitive or complex types.

We do not, however, currently support the same semantics against the path that specifies the same collection. That is, a PUT to customers(1) that contains nested orders replaces the orders for customer 1, but a PUT to customers(1)/orders is not currently specified if orders is a collection of entities (though it is if orders is a collection of complex types).Â



--
This message was sent by Atlassian JIRA
(v7.7.2#77003)


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