[jira] Commented: (DERBY-3080) With TERRITORY_BASED collation, when multiple characters map to a single collation element '_' matches a single collation element rather than a single character

["Mamta A. Satoor (JIRA)" <ji...@apache.org>]

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

Mamta A. Satoor commented on DERBY-3080:
----------------------------------------

Kathey, I think what you are seeing is the expected behavior ie I believe _ should match whatever the Collator for the given locale thinks is a single character. So, for the specific example above in Norwegian, the Collator for Nrowegian treats 'aa' as a single character and hence _ in pattern finds 'aa' as the matching character. 

There was some discussion about this topic in following thread http://www.nabble.com/Language-based-matching-tf1908121.html#a5222887 

> With TERRITORY_BASED collation, when multiple characters map to a single collation element '_'  matches a single collation element rather than a single character
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-3080
>                 URL: https://issues.apache.org/jira/browse/DERBY-3080
>             Project: Derby
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 10.3.1.4, 10.4.0.0
>            Reporter: Kathey Marsden
>
> '_' matches a single collation element rather than a single character if multiple characters have a single collation element.  Below is an example with norwegian aa  This occurs also with the patch for DERBY-2967 which addresses the case of matching of a  single character having more than one collation element.
> ij> connect 'jdbc:derby:wombat;create=true;territory=no_NO;collation=TERRITORY_BASED';
> ij> drop table t;
> 0 rows inserted/updated/deleted
> ij> create table t (vc varchar(30));
> 0 rows inserted/updated/deleted
> ij> insert into t values('middleaavalue');
> 1 row inserted/updated/deleted
> -- The query below should match
> ij> select * from t where vc like 'middle__value';
> VC
> ------------------------------
> 0 rows selected
> -- The query below should not match.
> ij>  select * from t where vc like 'middle_value';
> VC
> ------------------------------
> middleaavalue

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