[
https://issues.apache.org/jira/browse/DERBY-2583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12501463
]
Mamta A. Satoor commented on DERBY-2583:
----------------------------------------
Some changes for code generation also went in as revision 538325 and 541370
> At code generation time, look at collation type to determine what kind of DVD
> should get generated for character types.
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-2583
> URL: https://issues.apache.org/jira/browse/DERBY-2583
> Project: Derby
> Issue Type: New Feature
> Components: SQL
> Affects Versions: 10.3.0.0
> Reporter: Mamta A. Satoor
> Assignee: Mamta A. Satoor
> Fix For: 10.3.0.0
>
> Attachments:
> DERBY2583_generate_right_DVD_for_character_DTD_v1_diff.txt,
> DERBY2583_generate_right_DVD_for_character_DTD_v1_stat.txt
>
>
> Currently, in Derby 10.2, we generate
> SQLChar/SQLVarchar/SQLLongvarchar/SQLClob for various SQL character types.
> All these DVDs have the default collation of UCS_BASIC.
> Starting 10.3, we should look at the collation type of the DTD before
> deciding what kind of DVD gets generated for SQL character types. If the
> collation type of the character type is terriotry based collation, then we
> should generate
> CollatorSQLChar/CollatorSQLVarchar/CollatorSQLLongvarchar/CollatorSQLClob
> rather than SQLChar/SQLVarchar/SQLLongvarchar/SQLClob. The CollatorSQLxxx
> DVDs will have the territory based collator associated with them and hence
> the collation order of these DVDs will be different than the DVDs with
> default collation of UCS_BASIC.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
