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-405) Deep Updates (public comment c201305e00008)

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

Hubert Heijkers commented on ODATA-405:

Like you thinking Ralf, think this would work just fine. 

Was thinking however, what if I wanted to replace a, contained presumably, optionally set, of entities? Could I put these inline and apply 'replace' semantics in that case as opposed to patch semantics when provided separately in the 'delta style' format as proposed?

The interesting thing maybe is the difference between deleting links and deleting entities themselves. Deleting entities themselves could be accomplished already by using DELETE against such entity in and combining it with a PATCH in a changeset within a batch. I presume allowing tombstones here instead in a single patch would be kind of shorthand for that? 

Do we say anything about the scope of the entities/links that are being deleted? I.o.w. do we limit the links that can be delete to have to be addressable from the entity we are patching? Should we take containment vs. references into account as a 'limit' to what can be done? I'm asking as I can imagine, at least in my case, that if no containment boundaries exists the locking context/transaction scope can be come quite complex. 

> Deep Updates (public comment c201305e00008)
> -------------------------------------------
>                 Key: ODATA-405
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-405
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData ATOM Format 
>    Affects Versions: V4.0_CSD01
>            Reporter: Stefan Drees
>             Fix For: V4.0_CSD02
> The public comment [c201305e00008](https://lists.oasis-open.org/archives/odata-comment/201305/msg00008.html) with title "Deep Updates" states:
> """
> In section   8.4 Deep Inserts of OData-Atom-Format-v4.0 it is stated that 
> "Deep inserts are not allowed in update operations using PUT or PATCH requests."
> This is a great pity, as supporting deep updates would enable the very common scenario of saving a document with its lines as a whole.
> Could it be possible to add this feature?
> """

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]