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-1141) Upsert: clarify upsert along nullable single-valued navigation path


    [ https://issues.oasis-open.org/browse/ODATA-1141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=69269#comment-69269 ] 

Ralf Handl commented on ODATA-1141:
-----------------------------------

George: for server-generated keys: if key is provided, relate and update target, otherwise create and relate new target entity

> Upsert: clarify upsert along nullable single-valued navigation path
> -------------------------------------------------------------------
>
>                 Key: ODATA-1141
>                 URL: https://issues.oasis-open.org/browse/ODATA-1141
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: Protocol
>    Affects Versions: V4.01_CS01
>         Environment: Proposed
>            Reporter: Ralf Handl
>             Fix For: V4.01_CS02
>
>
> Section 11.4.4 Upsert an Entity allows upsert request to any URL that identifies a single entity. It then references section 11.4.2 Create an Entity, which only talks about creating entities in a collection
> Clarify that upsert is also valid along a nullable single-valued navigation property, at least as long the key property values are client-defined. May also work with server-defined keys by responding with 201 and a location header with the canonical URL of the newly created entity.



--
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]