[ 
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_CollationSensitiverShells_stat_v2.txt
                DERBY2416_CollationSensitiverShells_diff_v2.txt

With patch DERBY2416_CollationSensitiverShells_diff_v2.txt, I am extending the 
patch attached yesterday 
(DERBY2416_CollationSensitiveVarcharShell_diff_v1.txt). This latest patch has 
collation sensitive subclasses for SQLVarchar, SQLLongvarchar and SLQClob. The 
collation sensitive subclass for SQLChar is already checked in as 
CollatorSQLChar. 

So, In brief, the change description for yesterday's patch applies to the patch 
I am attaching right now. In addition, it applies the same logic for creating 
subclasses for SQLVarchar, SQLLongvarchar and SLQClob.

These classes are not hooked into Derby runtime yet and hence won't impact the 
existing tests.  

I will go ahead and commit this patch, so I can make more progress on language 
based ordering task. If anyone has any comments on this patch, please let me 
know about them and I can address them in subsequent patches. 



> Provide a shell for a subclass of SQLChar and SQLVarch which will use the 
> passed Collator to do the collation rather than the 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_CollationSensitiverShells_diff_v2.txt, 
> DERBY2416_CollationSensitiverShells_stat_v2.txt, 
> DERBY2416_CollationSensitiveVarcharShell_diff_v1.txt, 
> DERBY2416_CollationSensitiveVarcharShell_stat_v1.txt, 
> DERBY2416_NewCharClassWithDifferentCollationSupport_diff_v1.txt, 
> DERBY2416_NewCharClassWithDifferentCollationSupport_diff_v2.txt, 
> DERBY2416_NewCharClassWithDifferentCollationSupport_diff_v3.txt, 
> DERBY2416_NewCharClassWithDifferentCollationSupport_stat_v1.txt, 
> DERBY2416_NewCharClassWithDifferentCollationSupport_stat_v2.txt, 
> DERBY2416_NewCharClassWithDifferentCollationSupport_stat_v3.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.

Reply via email to