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] Created: (ODATA-411) Reconsider placement and semantics of OnDelete element

Reconsider placement and semantics of OnDelete element

                 Key: ODATA-411
                 URL: http://tools.oasis-open.org/issues/browse/ODATA-411
             Project: OASIS Open Data Protocol (OData) TC
          Issue Type: Improvement
          Components: OData CSDL
    Affects Versions: V4.0_CSD01
         Environment: [Proposed]
            Reporter: Ralf Handl
             Fix For: V4.0_CSD02

Currently the OnDelete element is on the dependent side and specifies "what happens here if over there the last thing goes away", i.e. an observer/event subscription pattern. This may have been inspired by SQL's ON DELETE, which is also specified on the dependent side.

The "original" OnDelete element of OData V2/V3 seems to be specified on the principal side of the association, unfortunately not explicitly stated, only deducible from the only given example:

  <Association Name="CProductCategory">
    <End Type="Self.CProduct" Multiplicity="*" />
    <End Type="Self.CCategory" Multiplicity="0..1">
      <OnDelete Action="Cascade" />

If the category goes away, it notifies its products to also go away.

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]