[
https://issues.apache.org/jira/browse/DERBY-2528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mamta A. Satoor closed DERBY-2528.
----------------------------------
> Set the correct collation type in SchemaDescriptor. The collation type will
> be UCS_BASIC for system schemas but it can be TERRITORY_BASED/UCS_BASIC for
> user schemas.
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-2528
> URL: https://issues.apache.org/jira/browse/DERBY-2528
> Project: Derby
> Issue Type: New Feature
> Components: SQL
> Affects Versions: 10.3.0.0
> Reporter: Mamta A. Satoor
> Assigned To: Mamta A. Satoor
> Attachments: DERBY2528_Collation_Type_In_Schema_v1_diff.txt,
> DERBY2528_Collation_Type_In_Schema_v1_stat.txt
>
>
> As per the wiki page
> http://wiki.apache.org/db-derby/BuiltInLanguageBasedOrderingDERBY-1478,
> Section Collation Determination, item 2)
> )<column definition> (of character string type) SQL spec Section 11.1 <schema
> definition>, General Rule 3 specifies that the character set associated with
> schema is used as the default character set for all <column definitions>.
> Based on this, character columns in user tables will have USER character set
> associated with them and hence collation type of UCS_BASIC/TERRITORY_BASED.
> The collation derivation will be implicit.
> In order for column definition to pick up the collation from the schema,
> correct collation type should be available in schema. In Derby implementation
> world, this translates having correct collation type in SchemaDescriptor.
> This jira entry is to track the work required in associating collation type
> to a SchemaDescriptor.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
