[
https://issues.apache.org/jira/browse/DERBY-1478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12470317
]
Mamta A. Satoor commented on DERBY-1478:
----------------------------------------
Rick, the latest functional spec is part of the Jira comment from me, dated Feb
2nd '07. It starts after this line in the comment "The functional spec now
looks as follows ".
I think as more comments get added to this Jira entry, it will be hard to track
down the functional spec in the Jira comments, so I will go ahead and attach it
as a file to Jira entry for easier lookup.
As for your specific questions about special treatement of ENGLISH locale, let
me take some time in looking up the SQL spec and existing code to see why Derby
might be using this for SQL identifiers. If somebody is aware of specific
Derby/Cloudscape history behind SQLUtil.SQLToUpperCase(), then please share
those.
> 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
>
> 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.
