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

Add build in functions operating on collections of primitive (and complex?) types

    Details

    • Type: New Feature
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: V4.0_ERRATA03
    • Fix Version/s: V4.01_CSD02
    • Component/s: URL Conventions
    • Labels:
    • Environment:

      Applied

    • Proposal:
      Hide

      Specify equality for collections of primitive types and extend the syntax, using the comma-separated list of literal primitive values enclosed by parens notation, to allow for comparison of arrays.
      Equality for ordered collections would be defined as:

      • same number of items
      • all items in the array, at the same index, compare as equal
        Equality for unordered collections would be defined as:
      • same number of items
      • all items in the array, after the server enforcing the same ordering on both collections, compare as equal, at the same index

      See also ODATA-1075

      Show
      Specify equality for collections of primitive types and extend the syntax, using the comma-separated list of literal primitive values enclosed by parens notation, to allow for comparison of arrays. Equality for ordered collections would be defined as: same number of items all items in the array, at the same index, compare as equal Equality for unordered collections would be defined as: same number of items all items in the array, after the server enforcing the same ordering on both collections, compare as equal, at the same index See also ODATA-1075
    • Resolution:
      Show
      https://www.oasis-open.org/committees/download.php/60941/odata-v4.01-wd02-part2-url-conventions-2017-06-07.docx

      Description

      I'm getting more asks for people wanting to filter against properties representing a collection of primitive type, most notably Collection(Edm.String).
      Things like equal to, not equal to and containing a value or subset are the operations that people are looking to do the most. The size of the array they can get around by using /$count.
      Short of coming up with something ourselves I was wondering if this is a more generic ask and if we could maybe guide implementations as to how to support this kind of functionality in a more generic way.

        Attachments

          Activity

            People

            • Assignee:
              handl Ralf Handl
              Reporter:
              hubert.heijkers Hubert Heijkers
            • Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: