db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Matrigali (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (DERBY-2717) throw error if non-matching collation ids in like.
Date Fri, 01 Jun 2007 17:55:16 GMT

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

Mike Matrigali resolved DERBY-2717.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 10.3.0.0

Fixed with svn 543554.  
Throw new error if operands of LIKE do not have matching collations.
Adds tests for this case in CollationTest2.java

> 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
>             Fix For: 10.3.0.0
>
>
> 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.


Mime
View raw message