[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (ODATA-749) What should service return when attempting to related two entities that are already related?
[ https://issues.oasis-open.org/browse/ODATA-749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=50440#comment-50440 ] Ralf Handl commented on ODATA-749: ---------------------------------- I vote for successful no-op: the intent of the request was to have these entities related, and this is the case. > What should service return when attempting to related two entities that are already related? > -------------------------------------------------------------------------------------------- > > Key: ODATA-749 > URL: https://issues.oasis-open.org/browse/ODATA-749 > Project: OASIS Open Data Protocol (OData) TC > Issue Type: Bug > Components: OData Protocol > Affects Versions: V4.0_ERRATA02 > Environment: [Proposed] > Reporter: Michael Pizzo > Priority: Minor > Fix For: V4.0_ERRATA03 > > > OData v4 protocol discusses how to add to the reference collection in a navigation property here: > 11.4.6.1 Add a Reference to a Collection-Valued Navigation Property > “A successful POST request to a navigation property's references collection adds a relationship to an existing entity. The request body MUST contain a single entity reference that identifies the entity to be added. See the appropriate format document for details. > On successful completion, the response MUST be 204 No Content and contain an empty body.” > It does not discuss what should happen if that reference already exists. Should this succeed as a no-op or should the service throw an error saying the record already exists? -- 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]