Re: Single character does not match high value unicode character with collation TERRITORY_BASED. Is this a bug

2007-07-23 Thread Mamta Satoor
Hi Kathey, I debugged the code below and it looks like _ not matching \uFA2D might be a bug. The actual code for comparison happens in the existing code that was left over for National character types. In SQLChar and in the newly introduced classes for collation, there are two methods public

Re: Single character does not match high value unicode character with collation TERRITORY_BASED. Is this a bug

2007-07-23 Thread Daniel John Debrunner
Mamta Satoor wrote: The method above uses the passed RuleBasedCollator to find the collation element for '_'. For our specific example, in Norwegian, '_' translates into only one collation element (vs 2 elements for '\uFA2D'). When looking for '_', we eliminate only 1 collation element from

Single character does not match high value unicode character with collation TERRITORY_BASED. Is this a bug

2007-07-20 Thread Kathey Marsden
With TERRITORY_BASED collation '_' does not match the character \uFA2D. It is the same for english or norwegian. FOR collation UCS_BASIC it matches fine. Could you tell me if this is a bug? Here is a program to reproduce. Kathey import java.sql.*; public class HighCharacter { public

Re: Single character does not match high value unicode character with collation TERRITORY_BASED. Is this a bug

2007-07-20 Thread Mamta Satoor
Kathey, let me take a look at this. thanks, Mamta On 7/20/07, Kathey Marsden [EMAIL PROTECTED] wrote: With TERRITORY_BASED collation '_' does not match the character \uFA2D. It is the same for english or norwegian. FOR collation UCS_BASIC it matches fine. Could you tell me if this is a