[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Updated: (ODATA-434) Introduce path segment for cross-joins on entity-container level
[ http://tools.oasis-open.org/issues/browse/ODATA-434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralf Handl updated ODATA-434: ----------------------------- Summary: Introduce path segment for cross-joins on entity-container level (was: Introduce path segment /$x for cross-joins on entity-container level) Proposal: Define path segment $crossjoin that takes a list of one or more entity set names as its parameters. The listed entity sets define the structure of the cross-join result, no abuse of $select any more, no "semantic overload" of the entity container. Example: GET ~/$crossjoin(Products,Customers)?$filter=Products/Name eq Customers/Name was:See summary Description: The current URL convention allows querying the cross-join of entity sets via requests targeting the entity container. This leads to potential name clashes: GET ~/Foo.Fred.Waldo can be a query targeting the entity container Waldo in schema Foo.Fred, or a query targeting entity set Waldo in container Fred of schema Foo. This clash can be avoided by using a path segment, similar to the path segment /$all that we use to address the union of all entities in a container. was: The current URL convention allows querying the cross-join of entity sets via requests targeting the entity container. This leads to potential name clashes: GET ~/Foo.Fred.Waldo can be a query targeting the entity container Waldo in schema Foo.Fred, or a query targeting entity set Waldo in container Fred of schema Foo. This clash can be avoided by appending a path segment /$x to the entity container name, similar to the path segment /$all that we use to address the union of all entities in a container. > Introduce path segment for cross-joins on entity-container level > ---------------------------------------------------------------- > > Key: ODATA-434 > URL: http://tools.oasis-open.org/issues/browse/ODATA-434 > Project: OASIS Open Data Protocol (OData) TC > Issue Type: Bug > Components: OData ABNF Construction Rules, OData URL Conventions > Affects Versions: V4.0_CSD01 > Environment: [Proposed] > Reporter: Ralf Handl > Fix For: V4.0_CSD02 > > > The current URL convention allows querying the cross-join of entity sets via requests targeting the entity container. > This leads to potential name clashes: > GET ~/Foo.Fred.Waldo > can be a query targeting the entity container Waldo in schema Foo.Fred, or a query targeting entity set Waldo in container Fred of schema Foo. > This clash can be avoided by using a path segment, similar to the path segment /$all that we use to address the union of all entities in a container. -- 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]