[OASIS Issue Tracker] Commented: (CMIS-762) Clarify the impact of repository specific collation

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ http://tools.oasis-open.org/issues/browse/CMIS-762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=35281#action_35281 ] 

Andy Hind commented on CMIS-762:
--------------------------------

Reading sections 4.2 and 8.2 of the SQL 92 spec comparisons are subject to collation.

See 8.2 note 3, relating to the comparison of strings

3) The comparison of two character strings is determined as fol-
            lows:

            a) If the length in characters of X is not equal to the length
              in characters of Y, then the shorter string is effectively
              replaced, for the purposes of comparison, with a copy of
              itself that has been extended to the length of the longer
              string by concatenation on the right of one or more pad char-
              acters, where the pad character is chosen based on CS. If
              CS has the NO PAD attribute, then the pad character is an
              implementation-dependent character different from any char-
              acter in the character set of X and Y that collates less
              than any string under CS. Otherwise, the pad character is a
              <space>.

            b) The result of the comparison of X and Y is given by the col-
              lating sequence CS.

            c) Depending on the collating sequence, two strings may com-
              pare as equal even if they are of different lengths or con-
              tain different sequences of characters. When the operations
              MAX, MIN, DISTINCT, references to a grouping column, and the
              UNION, EXCEPT, and INTERSECT operators refer to character
              strings, the specific value selected by these operations from
              a set of such equal values is implementation-dependent.

            Note: If the coercibility attribute of the comparison is
            Coercible, then the collating sequence used is the default de-
            fined for the character repertoire. See also other Syntax Rules
            in this Subclause, Subclause 10.4, "<character set specifi-
            cation>", and Subclause 11.28, "<character set definition>".

> Clarify the impact of repository specific collation
> ---------------------------------------------------
>
>                 Key: CMIS-762
>                 URL: http://tools.oasis-open.org/issues/browse/CMIS-762
>             Project: OASIS Content Management Interoperability Services (CMIS) TC
>          Issue Type: Improvement
>          Components: Domain Model
>    Affects Versions: V1.1 Errata
>            Reporter: Andy Hind
>             Fix For: V1.1 Errata
>
>
> 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. 
>   

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira