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] Commented: (ODATA-304) Add TargetKey attribute to <PropertyRef> within a <ReferentialConstraint>

    [ http://tools.oasis-open.org/issues/browse/ODATA-304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=32994#action_32994 ] 

Ralf Handl commented on ODATA-304:

Formerly we had the restriction that we had to specify a dependent property for each KEY property of the principal type.

We do have situations were we'd like to express a referential constraint to a non-key property of the principal type because that property has been "denormalized" into the dependent property. Which can be very convenient for the client in read scenarios, and is important information in edit scenarios, so I'd like to loosen this restriction to allow MORE than the key properties in referential constraints.

Are there also scenarios where designers want to specify LESS than all key properties?

> Add TargetKey attribute to <PropertyRef> within a <ReferentialConstraint>
> -------------------------------------------------------------------------
>                 Key: ODATA-304
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-304
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData CSDL
>    Affects Versions: V4.0_WD01
>         Environment: [Proposed]
>            Reporter: Michael Pizzo
>            Assignee: Ralf Handl
>             Fix For: V4.0_WD01
> Today we require that a <ReferentialConstraint> element contain the same number of <PropertyRef> elements, in the same order, as the <PropertyRef> elements of the <Key> of the related entity.
> This is the only place where we rely on the ordering of the properties of the key.
> We should instead add a TargetKey attribute to explicitly specify the key property of the related entity to which a <PropertyRef> within a <ReferentialConstraint> applies.

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]