[
https://issues.apache.org/jira/browse/DERBY-2416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mamta A. Satoor updated DERBY-2416:
-----------------------------------
Attachment: DERBY2416_NewCharClassWithDifferentCollationSupport_stat_v2.txt
DERBY2416_NewCharClassWithDifferentCollationSupport_diff_v2.txt
I am attaching a new patch,
DERBY2416_NewCharClassWithDifferentCollationSupport_diff_v2.txt which has
incorporated some of the feedback on the first patch.
1)I have renamed the new class as CollatorSQLChar
2)I have renamed intArray as collationElementsForString
3)I have renamed intLength as countOfCollationElements
4)Added javadocs for the fields and methods.
5)I have changed the javadoc for the class to talk in terms of
RuleBasedCollator rather than the interface Collator because the class is using
RuleBasedCollator.
I will commit this patch in few more minutes but if anyone has any further
comments on this patch, please feel free to raise them. I can address those
comments in a followup patch.
> Provide a shell for a subclass of SQLChar which will use the passed Collator
> to do the collation rather than SQLChar's default collation of UCS_BASIC
> -----------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-2416
> URL: https://issues.apache.org/jira/browse/DERBY-2416
> Project: Derby
> Issue Type: New Feature
> Components: SQL
> Affects Versions: 10.3.0.0
> Reporter: Mamta A. Satoor
> Assigned To: Mamta A. Satoor
> Attachments:
> DERBY2416_NewCharClassWithDifferentCollationSupport_diff_v1.txt,
> DERBY2416_NewCharClassWithDifferentCollationSupport_diff_v2.txt,
> DERBY2416_NewCharClassWithDifferentCollationSupport_stat_v1.txt,
> DERBY2416_NewCharClassWithDifferentCollationSupport_stat_v2.txt
>
>
> This jira entry is one of the tasks involved in implementing DERBY-2336.
> The existing SQLChar datatype has the Derby's default collation which is
> UCS_BASIC defined on them. With Derby 10.3, we want to support an additional
> collation for char datatypes which will be based on the territory. This jira
> issue is the placeholder for creating subclass of SQLChar which will use the
> passed Collator to do the collation. The current use of this class in Derby
> 10.3 will be for territory based collation but this class can be used in
> future for other kinds of collations like case-insensitive etc.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
