[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (ODATA-480) $batch: remove restriction "within the same change set " for Content-ID referencing
[ https://issues.oasis-open.org/browse/ODATA-480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=60659#comment-60659 ] Michael Pizzo commented on ODATA-480: ------------------------------------- There are really two different topics in this issue. Allowing Content-ID referencing across change sets and supporting $expand for POST. For the first (which is what is addressed in the proposal) we need a way for clients to determine which services support this and which do not (since existing 4.0 services will almost certainly not support this). > $batch: remove restriction "within the same change set " for Content-ID referencing > ----------------------------------------------------------------------------------- > > Key: ODATA-480 > URL: https://issues.oasis-open.org/browse/ODATA-480 > Project: OASIS Open Data Protocol (OData) TC > Issue Type: Improvement > Components: OData Batch Processing Format > Affects Versions: V4.0_CSD03 > Environment: [Proposed] > Reporter: Ralf Handl > Assignee: Ralf Handl > Labels: AdoptionBlocker > Fix For: V4.01_WD01 > > > Currently we restrict content-id referencing to entities created within the same change set. As we define that the content-id must be unique within a batch request, this is unnecessary. > Also we currently do not allow specifying $expand for POST requests, so there's no way to create an entity and in the same (batch) request retrieve the new entity together with related entities. -- 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]