[
https://issues.apache.org/jira/browse/DERBY-2416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12479793
]
Daniel John Debrunner commented on DERBY-2416:
----------------------------------------------
Looking at RulesBasedCollator more it is probably better to require that the
collator be of that type, it seems to have a more flexible api than the pure
Collator.
And for the performance stuff, I agree if you can get the functionality working
then the performance improvements should be somewhat easy since the code will
be fairly self-contained in these classes.
> 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_stat_v1.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.
