You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Mamta A. Satoor (JIRA)" <ji...@apache.org> on 2007/05/29 19:38:16 UTC
[jira] Commented: (DERBY-2717) throw error if non-matching
collation ids in like.
[ https://issues.apache.org/jira/browse/DERBY-2717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12499861 ]
Mamta A. Satoor commented on DERBY-2717:
----------------------------------------
When we fix this bug, we should add some test cases for LIKE and parameters combination.
> 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: 10.3.0.0
> Reporter: Mike Matrigali
> Assignee: Mike Matrigali
>
> 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.