[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (ODATA-678) Clarify delta responses with containment, OnDelete, or referential constraints
[ https://tools.oasis-open.org/issues/browse/ODATA-678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Pizzo updated ODATA-678: -------------------------------- Environment: [Applied] (was: [Proposed]) > Clarify delta responses with containment, OnDelete, or referential constraints > ------------------------------------------------------------------------------ > > Key: ODATA-678 > URL: https://tools.oasis-open.org/issues/browse/ODATA-678 > Project: OASIS Open Data Protocol (OData) TC > Issue Type: Improvement > Components: OData JSON Format, OData Protocol > Affects Versions: V4.0_OS > Environment: [Applied] > Reporter: Ralf Handl > Assignee: Michael Pizzo > Fix For: V4.0_ERRATA01 > > > If an entity is deleted, related entities will be implicitly deleted if a navigation property specifies <OnDelete Action="Cascade" /> or ContainsTarget="true". > It is not explicitly specified if in this case the service has to include a deleted-entity object for each deleted entity in a delta response, or whether it is sufficient to notify clients of the deletion of the principal entity. > Similarly in the presence of referential constraints added the changed entities already carry the necessary information and the added/deleted link objects are redundant. > The JSON Format design goal of omitting everything from the payload that can be deduced from $metadata would indicate to just notifying the deletion of the principal entity. -- 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]