Make key aliases optional, clarify multiple to-one navigation hops

XMLWordPrintable

    • Type: New Feature
    • Resolution: Unresolved
    • Priority: Major
    • V5.0
    • Affects Version/s: V4.01_OS
    • Component/s: CSDL JSON, CSDL XML, URL Conventions
    • None
    • Environment:

      Proposed

    • Hide

      CSDL:

      • Make key aliases optional for keys with a path.
      • Clarify that multiple non-nullable to-one navigation hops can occur if the referenced key property of the directly related entity type itself is referenced from a directly related entity type etc.

      URL Conventions:

      • If no key alias is provided for a related/nested primitive property, use the dash-separated path in parentheses-style keys, e.g. /something(foo-bar-id='abc')
      Show
      CSDL: Make key aliases optional for keys with a path. Clarify that multiple non-nullable to-one navigation hops can occur if the referenced key property of the directly related entity type itself is referenced from a directly related entity type etc. URL Conventions: If no key alias is provided for a related/nested primitive property, use the dash-separated path in parentheses-style keys, e.g. /something(foo-bar-id='abc')

      When using an "association to one" as a key component, it is currently required to provide an alias for use in parentheses-style key syntax.

      This can lead to "funny" aliases when the OData model is automatically derived from a conceptual model that does not know about OData key syntax.

            Assignee:
            Unassigned
            Reporter:
            handl
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: