[OASIS Issue Tracker] Commented: (ODATA-274) OData clients should always use PATCH, deprecate PUT

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ http://tools.oasis-open.org/issues/browse/ODATA-274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=32468#action_32468 ] 

Ralf Handl commented on ODATA-274:
----------------------------------

I like this, and we even can use PATCH for "UPSERT", see https://tools.ietf.org/html/rfc5789#section-2:

If the Request-URI does not point to an existing resource, the server MAY create a new resource, depending on the patch document type (whether it can logically modify a null resource) and permissions, etc.

> OData clients should always use PATCH, deprecate PUT
> ----------------------------------------------------
>
>                 Key: ODATA-274
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-274
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData Protocol v1.0, OData URL Conventions v1.0
>         Environment: [Proposed]
>            Reporter: Michael Pizzo
>
> PUT semantics call for setting to null any properties not specified in the payload. PATCH semantics apply the specified properties but leave unspecified properties unchanged.
> Specifying that clients ALWAYS use PATCH for updates is much safer for round-tripping data. For example, open properties, aggregated values, additive schema changes, and computed projections could all add additional properties to the payload that the client should be able to safely ignore. If the client uses PATCH to update then they do not lose information, but if the client ignores properties and uses PUT to update they will likely lose data in round-tripping.
> OData clients should always use PATCH when doing updates.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira