[OASIS Issue Tracker] Updated: (ODATA-165) Support Cross-joins

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

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

Ralf Handl updated ODATA-165:
-----------------------------

    Environment: [Applied]  (was: [Applied to URL Conventions])
    Component/s:     (was: OData Protocol )

Did not apply to Protocol as it only talks about querying collections without listing which kind of collection, and entity container now behaves like a collection.

> Support Cross-joins
> -------------------
>
>                 Key: ODATA-165
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-165
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: New Feature
>          Components: OData ABNF Construction Rules, OData URL Conventions 
>    Affects Versions: V4.0_WD01
>         Environment: [Applied]
>            Reporter: Michael Pizzo
>            Assignee: Ralf Handl
>             Fix For: V4.0_CSD02
>
>
> We often have requests to support queries that span entitysets. Where navigation properties exist between the entitysets these provide a natural and convenient mechanism for building queries that span entitysets. However, where navigation properties are not present a way is needed to build such cross-entity spanning queries.
> In the context of looking at aggregation we came up with a solution for doing this by considering the entitycontainer as the cross-product of the contained entitysets. You could then $expand the entitysets you wanted to join, and add a filter to specify the equivalent of the join condition. This seemed generally useful beyond just the scope of aggregation.

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