db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mamta A. Satoor (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-2717) throw error if non-matching collation ids in like.
Date Fri, 01 Jun 2007 18:44:15 GMT

    [ https://issues.apache.org/jira/browse/DERBY-2717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12500806

Mamta A. Satoor commented on DERBY-2717:

Mike, I probably didn't spend enough time on the patch to understand this but why is DataTypeDescriptor.getCollationName()
not simply calling typeDescriptor.getCollationName()? Also, if we do need to keep DataTypeDescriptor.getCollationName()
the way it is right now, then maybe we should use constants strings from StringDataValue for
collation names rather than hardcoded strings "UCS_BASIC" and "TERRITORY_BASED".

> throw error if non-matching collation ids in like.
> --------------------------------------------------
>                 Key: DERBY-2717
>                 URL: https://issues.apache.org/jira/browse/DERBY-2717
>             Project: Derby
>          Issue Type: Sub-task
>          Components: SQL
>    Affects Versions:
>            Reporter: Mike Matrigali
>            Assignee: Mike Matrigali
>             Fix For:
> LIKE should throw an error  if it has mismatching params.  
> Mamta gives the standard references:
> The collation rule for c1 like c2 should be same as c1 = c2 as per SQL specification.
> As per SQL spec, Section 8.5 <like predicate>, Syntax Rules 3d),
> "The collation used for <like predicate> is determined by applying Subclause 9.13,
"Collation determination", with operands CVE, PC, and (if specified) EC."
> As per SQL spec, Section 8.2 <comparison predicate>, General Rules 3a),
> "Let CS be the collation as determined by Subclause 9.13, "Collation determination",
for the declared types of the two character strings."
> Please let me know if you have any further questions in this area.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message