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-613) Allow PATCH to entity sets using the delta-response format


     [ https://issues.oasis-open.org/browse/ODATA-613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Pizzo updated ODATA-613:
--------------------------------

    Description: 
This will allow easy synchronization between services with same model

Previous proposal (for sanity check):

Document changes:
part1-protocol

Add section: 11.4.10 Update an Entity Set
To update a collection, the client sends a PATCH request to that collection's URL. The PATCH body MUST contain a valid delta response consisting of appropriate representations for 
If the target URL for the collection is a navigation link, any added entity is automatically linked to the entity containing the navigation link, and any deleted entity is automatically unlinked.

  was:This will allow easy synchronization between services with same model

       Proposal: 
PATCH to a collection of entities can take a delta payload (assumed delta format if an array) ODATA-613

*MUST NOT have $filter, $select, $orderby, etc. 


  was:
Document changes:
part1-protocol

Add section: 11.4.10 Update an Entity Set
To update a collection, the client sends a PATCH request to that collection's URL. The PATCH body MUST contain a valid delta response consisting of appropriate representations for entities (either added or changed), or deleted entities, as well as added or deleted links between entities.

Entity representations in the delta response are processed as an update (link to 11.4.3) if they are already related and upserted otherwise (link to 11.4.4), deleted entities are processed as such (link to 11.4.5). Added links with a relationship of a single-valued navigation property are processed as a reference change for that navigation property (link to 11.4.6.3). Added links with a relationship of a multi-valued navigation property are processed as added references for that navigation property (link to 11.4.6.1).  Deleted links with a relationship of a multi-valued navigation property are processed as removed references for that navigation property (link to 11.4.6.2). 

If the target URL for the collection is a navigation link, any added entity is automatically linked to the entity containing the navigation link, and any deleted entity is automatically unlinked.


> Allow PATCH to entity sets using the delta-response format
> ----------------------------------------------------------
>
>                 Key: ODATA-613
>                 URL: https://issues.oasis-open.org/browse/ODATA-613
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData JSON Format, OData Protocol
>    Affects Versions: V4.0_OS
>         Environment: Set Operations, [Proposed]
>            Reporter: Ralf Handl
>            Assignee: Ralf Handl
>              Labels: Usability
>             Fix For: V4.01_WD01
>
>
> This will allow easy synchronization between services with same model
> Previous proposal (for sanity check):
> Document changes:
> part1-protocol
> Add section: 11.4.10 Update an Entity Set
> To update a collection, the client sends a PATCH request to that collection's URL. The PATCH body MUST contain a valid delta response consisting of appropriate representations for 
> If the target URL for the collection is a navigation link, any added entity is automatically linked to the entity containing the navigation link, and any deleted entity is automatically unlinked.



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