Define semantics for PUT against a single entity with nested content

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major
    • V4.01_WD01
    • Affects Version/s: V4.0_ERRATA03
    • Component/s: Protocol
    • None
    • Environment:

      [Proposed]

    • Hide

      Align Semantics of PUT with PATCH, as specified in ODATA-876, by specifying that, when you do a PUT,
      1) You can include new nested entities, existing entities, and references to existing entities
      2) Existing entities are updated using PUT semantics
      a) entities to be updated must have either @odata.id or key fields, otherwise interpreted as an insert
      b) if @odata.id and key fields both exist but don't match, then request is invalid
      3) The end result of the PUT is that the specified entities and entity references are the full set of entities related according to that relationship.

      Show
      Align Semantics of PUT with PATCH, as specified in ODATA-876 , by specifying that, when you do a PUT, 1) You can include new nested entities, existing entities, and references to existing entities 2) Existing entities are updated using PUT semantics a) entities to be updated must have either @odata.id or key fields, otherwise interpreted as an insert b) if @odata.id and key fields both exist but don't match, then request is invalid 3) The end result of the PUT is that the specified entities and entity references are the full set of entities related according to that relationship.

      In ODATA-666 we defined semantics for a PATCH request to a single entity or collection of entities that contained nested entities.

      We said it didn't make sense to do a PUT against a collection of entities, but need to define the semantics (if allowed) of a PUT operation against a single entity where the payload contains nested entities.

            Assignee:
            Michael Pizzo (Inactive)
            Reporter:
            Michael Pizzo (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: