db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Matrigali (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-2377) Document language based ordering which will be implemented by code related sub-tasks of DERBY-1478.
Date Thu, 07 Jun 2007 19:14:26 GMT

     [ https://issues.apache.org/jira/browse/DERBY-2377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Mike Matrigali updated DERBY-2377:
----------------------------------


I've reviewed all the attachments and am ok with commit of them.

I think the following is a little unclear, but would not hold up commit:
Non-default collation support is provided through the java.text.RuleBasedCollator class and
the set of rules associated with the specified territory of the JVM.

I want it to be clear that each JVM can support many territories, it has a set of rules for
each of these territories and it is independent of the the default territory of the JVM. 


> Document language based ordering which will be implemented by code related sub-tasks
of DERBY-1478.
> ---------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-2377
>                 URL: https://issues.apache.org/jira/browse/DERBY-2377
>             Project: Derby
>          Issue Type: Sub-task
>          Components: Documentation
>    Affects Versions: 10.3.0.0
>            Reporter: Mamta A. Satoor
>            Assignee: Laura Stewart
>         Attachments: cdevcollation.html, cdevcollation.html, cdevcollation.html, cdevcollation.html,
cdevdvlp51654.html, cdevdvlp51654.html, derby2377_1.diff, rrefattribcollation.html, rrefattribcollation.html,
tdevdvlpcollation.html, tdevdvlpcollation.html
>
>
> There is an effort going on to implement language based ordering. This will be implemented
by various code-related subtasks of DERBY-1478. The functional spec is attached to DERBY-1478.
This feature will need accompanying documentation changes and this Jira entry is to track
that work.

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