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] Updated: (ODATA-61) Allow complex properties or components of complex properties as parts of a referential constraint


     [ http://tools.oasis-open.org/issues/browse/ODATA-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ralf Handl updated ODATA-61:
----------------------------

    Proposal: 
Rephrase second paragraph of section 11.7 to

The edm:Principal element and the edm:Dependent element MUST each contain the same number of edm:PropertyRef elements. The property references MUST be ordered consistently in the principal and dependent elements. The property references MUST have the same data types in the principal and dependent elements.

Add after third paragraph: 

The property references for the dependent entity MUST be path expressions resolving to primitive properties of the entity type itself or to primitive properties of complex properties (recursively) of the entity type. 

  was:Use same extended syntax for PropertyRef within Principal and Dependend as proposed in ODATA-60 for PropertyRef within Key.


> Allow complex properties or components of complex properties as parts of a referential constraint
> -------------------------------------------------------------------------------------------------
>
>                 Key: ODATA-61
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-61
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData CSDL v1.0
>    Affects Versions: WD01
>         Environment: [Proposed]
>            Reporter: Ralf Handl
>             Fix For: WD01
>
>
> Complex types may be used to semantically structure an entity type, e.g. grouping an Amount and a CurrencyCode into a complex type MonetaryAmount. 
> Properties of complex types need to take the role of a dependent in a referential constraint, expressing e.g. that the CurrencyCode of the above complex type must only take values defined by the key property Code of a Currency entity type:
> <ReferentialConstraint>
>   <Principal Role="Currency">
>     <PropertyRef Name="Code" />
>   </Principal>
>   <Dependent Role="OrderItem">
>     <PropertyRef Name="ItemPrice/CurrencyCode" />
>   </Dependent>
> </ReferentialConstraint>

-- 
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]