db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mamta A. Satoor (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-1478) Add built in language based ordering and like processing to Derby
Date Thu, 29 Mar 2007 19:28:25 GMT

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

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

The code work that will go in for this feature can be extended by someone with the itch to
provide case-insensitive search support. Currently, with this feature, the Collator will be
determined by Derby code from the territory and it will be passed to Collator sensitive CHAR
classes so that can do collation based on that. Somebody would need to do the coding work
to get the correct Collator for case-insensitive search and pass that it to Collator sensitive
CHAR classes.

So, in short, at the end of this feature, an end user can't simply configure Derby to do case-insensitive
search rather than territory based search. Some Derby coding will be required to enable case-insensitive
search.

> 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
>
>
> 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