[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Created: (ODATA-244) Support navigation properties on complex types
Support navigation properties on complex types ---------------------------------------------- Key: ODATA-244 URL: http://tools.oasis-open.org/issues/browse/ODATA-244 Project: OASIS Open Data Protocol (OData) TC Issue Type: Improvement Components: OData Protocol v1.0 Affects Versions: WD01 Environment: [Proposed] Reporter: Michael Pizzo Assignee: Michael Pizzo Priority: Minor Fix For: WD01 Today navigation properties must be direct children of the entity. We should support navigation properties being defined on properties grouped into a complex type. For example: <ComplexType Name="Address"> <Property Name="Street" Type="Edm.String" /> <NavigationProperty Name="City" Type="MyModel.City" /> <NavigationProperty Name="Region" Type="MyModel.Region" /> <NavigationProperty Name="Country" Type="MyModel.Country" /> </ComplexType> If a type <Person> has an Address, then you could express the navigation property binding as: <EntitySet Name="People" Type="Person"> <NavigationPropertyBinding Path="Address/City" EntitySet="Cities"/> <NavigationPropertyBinding Path="Address/Region" EntitySet="Regions"/> <NavigationPropertyBinding Path="Address/Country" EntitySet="Countries"/> </EntitySet> -- 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]