[
https://issues.apache.org/jira/browse/DERBY-2670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Matrigali updated DERBY-2670:
----------------------------------
I have logged DERBY-2706 for the new problems you found knut. My first guess
is that this is not related to the previous problem, thus logged a new issue.
Of course won't really know until it is fixed. If you come up with any other
cases that
you think would be worthwhile add them to that issue and hopefully we can
eventually get them into a junit test.
> %a% and %aa% match too many rows in database with collation=TERRITORY_BASED
> and territory=no_NO
> -----------------------------------------------------------------------------------------------
>
> Key: DERBY-2670
> URL: https://issues.apache.org/jira/browse/DERBY-2670
> Project: Derby
> Issue Type: Bug
> Components: SQL
> Affects Versions: 10.3.0.0
> Reporter: Knut Anders Hatlen
> Assigned To: Mike Matrigali
> Fix For: 10.3.0.0
>
> Attachments: coll.java, collrepro.sql
>
>
> On a database with territory=no_NO and collation=TERRITORY_BASED, I get these
> results from a query which uses the LIKE predicate:
> ij> select * from t where x like '%a%';
> X
> --------------------
> Waagan
> Wåhan
> Wanvik
> Wågan
> ekstrabetaling
> ekstraarbeid
> a
> a
> -a
> a
> B
> C
> 12 rows selected
> The last two rows ('B' and 'C') should not have been included in the result,
> since they do not match the pattern '%a%'.
> Similar wrong results are seen with '%aa%':
> ij> select * from t where x like '%aa%';
> X
> --------------------
> Waagan
> ekstraarbeid
> B
> 3 rows selected
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
