Clarify the impact of repository specific collation

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major
    • V1.1 Errata
    • Affects Version/s: V1.1 Errata
    • Component/s: Domain Model
    • None
    • Hide

      I think a note in 2.1.14.2.4.1 something like:

      The collation rules used to evaluate comparison predicates for String properties are repository specific.
      For example, a predicate of the form
      ... where cmis:name LIKE 'a%' ...
      MUST match a cmis:name starting with 'a' and may match a cmis:name starting with 'A'

      Show
      I think a note in 2.1.14.2.4.1 something like: The collation rules used to evaluate comparison predicates for String properties are repository specific. For example, a predicate of the form ... where cmis:name LIKE 'a%' ... MUST match a cmis:name starting with 'a' and may match a cmis:name starting with 'A'

      The 1.1 specification only mentions repository specific collation with respect to query and ordering - section 2.1.14.2.5

      Repository specific collation may also be expected to affect any string comparison predicates and LIKE.
      (SQL 92 says the behaviour depends on the collation)

      For example, some databases have a default collation which is case-sensitive and others the reverse.

            Assignee:
            Unassigned
            Reporter:
            Andy Hind (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated: