[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Updated: (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:all-tabpanel ]
Stefan Drees updated ODATA-304:
-------------------------------
Resolution:
Accepted: https://www.oasis-open.org/committees/download.php/49026/odata-meeting-34_on-20130425_26-F2F-minutes.html#odata-304
> 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]