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] Commented: (ODATA-274) OData clients should always use PATCH, deprecate PUT

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

Ralf Handl commented on ODATA-274:

We should define what "additive schema changes" are:
- add property that is nullable or has a default value
- add navigation property that is nullable or collection-valued
- add entity type
- add entity set
- add function (import)
- add function parameter that is nullable or has a default value
- add annotations

To be discussed:
- change property from Nullable="false" to Nullable="true"
- change String property from FixedLength="true" to FixedLength="false"
- change property to larger MaxLength, Precision or Scale

- all modifying operations that succeed on "old" schema will succeed on new schema
- clients will receive at least the information of the old schema (treating additional NULL values as information: larger value range :-)

> 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
>    Affects Versions: V4.0_WD01
>         Environment: [Proposed]
>            Reporter: Michael Pizzo
>             Fix For: V4.0_WD01
> 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


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