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-615) Allow PATCH and DELETE with $filter on collections to modify or delete all (and only) the matching entities


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

Michael Pizzo updated ODATA-615:
--------------------------------

    Proposal: 
1)	DELETE to any collection with a $filter clause removes any element matching that filter. [ODATA-616], [ODATA-615]
a.	$select, $orderby, $top, $skip are NOT expected to be supported
2)	PUT against a collection of primitive/complex types takes a collection in the payload and replaces the entire collection. [ODATA-615]
a.	PUT does not support $filter.
b.	This is the existing 4.0 behavior
3)	PUT is not supported against an entity collection  [ODATA-615]
4)	PATCH to any collection with a payload containing a single value updates each element in the collection [ODATA-615]
a.	If $filter is present, applies patch to those items matching the $filter [ODATA-615]
5)	PATCH to a collection of primitive or complex types with a collection payload is not supported  [ODATA-615]


  was:
1)	DELETE to any collection with a $filter clause removes any element matching that filter.
a.	$select, $orderby, $top, $skip are NOT expected to be supported
2)	PUT against a collection of primitive/complex types takes a collection in the payload and replaces the entire collection.
a.	PUT does not support $filter.
b.	This is the existing 4.0 behavior
3)	PUT is not supported against an entity collection 
4)	PATCH to any collection with a payload containing a single value updates each element in the collection 
a.	If $filter is present, applies patch to those items matching the $filter 
5)	PATCH to a collection of primitive or complex types with a collection payload is not supported 




> Allow PATCH and DELETE with $filter on collections to modify or delete all (and only) the matching entities
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: ODATA-615
>                 URL: https://issues.oasis-open.org/browse/ODATA-615
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData Protocol, OData URL Conventions
>    Affects Versions: V4.0_OS
>         Environment: Set Operations; [Proposed]
>            Reporter: Ralf Handl
>            Assignee: Ralf Handl
>              Labels: Usability
>             Fix For: V4.01_WD01
>
>
> Another natural extension
> Previous proposal: 
> (was 11.4.3) 11.4.3.1 Update a Single Entity
> (add this first sentence to explain the expected request URL) To update a single entity in a collection, the client sends a PATCH or POST request to an entity's edit URL. 
> 11.4.3.2 Updating Multiple Entities
> To update multiple entities in a collection, the client sends a PATCH request to that collection's URL.
> The URL may include a $filter query option restricting the entities to be updated. For the entities matching the filter expression or all entities in the collection if no $filter query option was given, the service handles the request as a request to update a single entity (link to 11.4.3.1). 
> On success, the response MUST be a valid success response (link to 9.1).
> On failure, the service MUST NOT update any of the qualifying entities.
> 11.4.5 Deleting Entities from a Collection
> (was 11.4.5) 11.4.5.1 Delete a Single Entity
> 11.4.5.2 Deleting Multiple Entities
> To delete multiple entities in a collection, the client sends a DELETE request to that collection's URL.
> The URL may include a $filter query option restricting the entities to be deleted. For the entities matching the filter expression or all entities in the collection if no $filter query option was given, the service handles the request as a request to delete a single entity (link to 11.4.5.1). 
> On success, the response MUST be 204 No Content (link to 9.1.4) and contain an empty body. .
> On failure, the service MUST NOT delete any of the qualifying entities.
> part2-url-conventions
> In section "5.1 System Query Options", change the sentence "POST requests to entity sets as well as all PUT and DELETE requests do not allow system query options." to "POST and PUT  requests to entity sets do not allow system query options."



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