Extend FilterExpressionRestrictions with "SearchExpression"

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major
    • V4.01_CSD02
    • Affects Version/s: V4.0_ERRATA03
    • Component/s: Vocabularies
    • None
    • Environment:

      Applied

    • Hide

      Add new allowed value

      <Record>
      <PropertyValue Property="Value" String="SearchExpression" />
      <Annotation Term="Core.Description" String="String property can be used as first operand in startswith, endswith, and contains clauses" />
      </Record>

      for properties representing character large objects.

      Show
      Add new allowed value <Record> <PropertyValue Property="Value" String="SearchExpression" /> <Annotation Term="Core.Description" String="String property can be used as first operand in startswith, endswith, and contains clauses" /> </Record> for properties representing character large objects.
    • Hide

      https://github.com/oasis-tcs/odata-vocabularies/commit/667abf5790bbc0ee75d10452c1cbd1985e7c4969

      Show
      https://github.com/oasis-tcs/odata-vocabularies/commit/667abf5790bbc0ee75d10452c1cbd1985e7c4969

      Filter expression restrictions where introduced in ODATA-816 to express restricted filter capabilities on individual properties that can only be used in equality comparison or interval comparison.

      Another important class of restrictions is for operators on character large objects (CLOB, NCLOB, TEXT). Many data stores only support null check and pattern matching on columns of this type and do not support equality or greater-than comparison.

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

              Created:
              Updated:
              Resolved: