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-1454) Allow upserts against media entities


Hubert Heijkers created ODATA-1454:
--------------------------------------

             Summary: Allow upserts against media entities
                 Key: ODATA-1454
                 URL: https://issues.oasis-open.org/browse/ODATA-1454
             Project: OASIS Open Data Protocol (OData) TC
          Issue Type: Improvement
          Components: Protocol
    Affects Versions: V4.01_ERRATA01, V4.0_ERRATA03
            Reporter: Hubert Heijkers


Section 11.4.4 in protocol mentions that upserts are not supported against media entities and, more importantly, that services MUST fail an update request to a URL that would identify such an entity if it does not exist.
Given the fact that the service can't be using service-generated keys for these entities and the client apparently already knows how to compose/identify the individual media entities in such collection, why not allow upserts as well?

PS Also noted that in v4.01 we've added "single-valued non-containment navigation properties" to the exclusions list as well. Couldn't quickly recall/figure out the issue but shouldn't that only be if there is no navigation property binding?



--
This message was sent by Atlassian Jira
(v8.3.3#803004)


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