Uploaded image for project: 'OASIS Open Data Protocol (OData) TC'
  1. OASIS Open Data Protocol (OData) TC
  2. ODATA-958

Capabilities: FilterRestrictions and SortRestrictions for navigation properties

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: V4.0_ERRATA02
    • Fix Version/s: V4.01_WD01
    • Component/s: Vocabularies
    • Labels:
      None
    • Environment:

      Annotations

    • Proposal:
      Hide

      Add three new properties, FilterFunctions, FilterRestrictions, and SortRestrictions, to Capabilities.NavigationPropertyRestriction, such that the full definition becomes:

      <ComplexType Name="NavigationPropertyRestriction">
      <Property Type="Edm.NavigationPropertyPath" Name="NavigationProperty">
      <Annotation Term="Core.Description" String="Navigation properties can be navigated"/>
      </Property>
      <Property Type="Capabilities.NavigationType" Name="Navigability">
      <Annotation Term="Core.Description" String="Navigation properties can be navigated to this level"/>
      </Property>
      <Property Type="Collection(Edm.String)" Name="FilterFunctions">
      <Annotation Term="Core.Description" String="List of functions and operators supported in $filter. If null, all functions and operators may be attempted."/>
      </Property>
      <Property Type="Capabilities.FilterRestrictionsType" Name="FilterRestrictions">
      <Annotation Term="Core.Description" String="Restrictions on $filter expressions"/>
      </Property>
      <Property Type="Capabilities.SortRestrictionsType" Name="SortRestrictions">
      <Annotation Term="Core.Description" String="Restrictions on $orderby expressions"/>
      </Property>
      </ComplexType>

      Show
      Add three new properties, FilterFunctions, FilterRestrictions, and SortRestrictions, to Capabilities.NavigationPropertyRestriction, such that the full definition becomes: <ComplexType Name="NavigationPropertyRestriction"> <Property Type="Edm.NavigationPropertyPath" Name="NavigationProperty"> <Annotation Term="Core.Description" String="Navigation properties can be navigated"/> </Property> <Property Type="Capabilities.NavigationType" Name="Navigability"> <Annotation Term="Core.Description" String="Navigation properties can be navigated to this level"/> </Property> <Property Type="Collection(Edm.String)" Name="FilterFunctions"> <Annotation Term="Core.Description" String="List of functions and operators supported in $filter. If null, all functions and operators may be attempted."/> </Property> <Property Type="Capabilities.FilterRestrictionsType" Name="FilterRestrictions"> <Annotation Term="Core.Description" String="Restrictions on $filter expressions"/> </Property> <Property Type="Capabilities.SortRestrictionsType" Name="SortRestrictions"> <Annotation Term="Core.Description" String="Restrictions on $orderby expressions"/> </Property> </ComplexType>
    • Resolution:
      Show
      https://github.com/oasis-tcs/odata-vocabularies/commit/49fcd7b5ce9ec172397a3592954ff9eb9ca9d56d

      Description

      With the addition of cross-service navigation we need means to express that a navigation property cannot be used in filter or sort expressions.

        Attachments

          Activity

            People

            • Assignee:
              mikep Michael Pizzo (Inactive)
              Reporter:
              handl Ralf Handl
            • Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: