Yes, Kim, I entered a documentation Jira entry sub-task for DERBY-1478. The
Jira entry number and description is as follows
"DERBY-2377 : Document language based ordering which will be implemented by
code related sub-tasks of DERBY-1478."

thanks,
Mamta


On 2/27/07, Kim Haase <[EMAIL PROTECTED]> wrote:

Hello, Mamta,

Thanks for implementing this attribute. It looks as if it needs to be
documented -- will you be filing a JIRA issue for the documentation?

Thanks,
Kim

Mamta A. Satoor (JIRA) wrote:
>      [
https://issues.apache.org/jira/browse/DERBY-2334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel]
>
> Mamta A. Satoor updated DERBY-2334:
> -----------------------------------
>
>     Derby Info:   (was: [Patch Available])
>        Summary: Accept the new collation attribute and store it as a
database property. Will be used for language based collation
ordering.  (was: Accept the new collation attribute and store it in
services.properties file. Will be used for language based collation
ordering.)
>
>> Accept the new collation attribute and store it as a database property.
Will be used for language based collation ordering.
>>
---------------------------------------------------------------------------------------------------------------------------
>>
>>                 Key: DERBY-2334
>>                 URL: https://issues.apache.org/jira/browse/DERBY-2334
>>             Project: Derby
>>          Issue Type: Sub-task
>>          Components: JDBC
>>    Affects Versions: 10.3.0.0
>>            Reporter: Mamta A. Satoor
>>         Assigned To: Mamta A. Satoor
>>         Attachments: DERBY2334_AcceptCollationAttribute_diff_V01.txt,
DERBY2334_AcceptCollationAttribute_diff_V02.txt,
DERBY2334_AcceptCollationAttribute_stat_V01.txt,
DERBY2334_AcceptCollationAttribute_stat_V02.txt
>>
>>
>> A user would specify the collation desired (UCS_BASIC or
TERRITORY_BASED_COLLATION) through the new jdbc url attribute - collation.
This attribute will be used to determine collation ordering for character
datatypes,
>

Reply via email to