db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "wayne townsend-merino (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-1478) Add built in language based ordering and like processing to Derby
Date Mon, 21 May 2007 21:58:16 GMT

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

wayne townsend-merino commented on DERBY-1478:
----------------------------------------------

It would be fantastic if we could set the collation on a per-field basis, as in:
     alter table foo modify bar varchar(10) COLLATE latin1_bin ;
This way, wouldn't we be able to do a case-sensitive search for a field, even if we set a
case-INsensitive collation for the database?  Let me know if I can help.



> 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, DERBY-1478_FunctionalSpecV2.html,
DERBY-1478_FunctionalSpecV3.html, DERBY-1478_FunctionalSpecV4.html, DERBY-1478_FunctionalSpecV5.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.


Mime
View raw message