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

Rick Hillegas commented on DERBY-1478:
--------------------------------------

Hi Mamta,

As I read part 2 of the SQL Standard, it looks like you need a CAST in order to 
compare 2 strings which have different collations bound to them. Both string 
operands must have the same collation--that is my reading of Syntax rule 3b in 
section 9.13. Sections 6.12 and 6.1 explain how to cast the operands so that 
you can compare them. I think you need to write an expression like this:

   WHERE userStringCol = CAST ( systemStringCol AS VARCHAR COLLATE 
userStringColumnsCollation )

Here's an example I googled up: 
http://docs.openlinksw.com/virtuoso/sqlrefDATATYPES.html. Hope this helps.

> Add built in language based ordering and like processing to Derby
> -----------------------------------------------------------------
>
>                 Key: DERBY-1478
>                 URL: https://issues.apache.org/jira/browse/DERBY-1478
>             Project: Derby
>          Issue Type: Improvement
>          Components: SQL
>    Affects Versions: 10.1.2.1
>            Reporter: Kathey Marsden
>         Assigned To: Mamta A. Satoor
>         Attachments: DERBY-1478_FunctionalSpecV1.html
>
>
> It would be good for Derby to have built in Language based ordering based on 
> locale specific Collator.
> Language based ordering is an important feature for international deployment. 
>  DERBY-533 offers one implementation option for this but according to the 
> discussion in that issue National Character Types carry a fair amount of 
> baggage with them especially in the form of concerns about conversion   to 
> and from datetime and number types. Rick  mentioned SQL language for 
> collations as an option for language based ordering. There may be other 
> options too, but I thought it worthwhile to add an issue for the high level 
> functional concern, so the best choice can be made for implementation without 
> assuming that National Character Types is the only solution.
> For possible 10.1 workaround and examples see:
> http://wiki.apache.org/db-derby/LanguageBasedOrdering

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

Reply via email to