db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mamta A. Satoor (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-2599) Set correct collation type and derivation on DataTypeDescriptor(DTD).
Date Thu, 31 May 2007 21:47:16 GMT

    [ https://issues.apache.org/jira/browse/DERBY-2599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12500505

Mamta A. Satoor commented on DERBY-2599:

The commit comments for revision 543266 are as follows
There are few character string types that should take their collation type from compilation
schema. I had earlier checked in code for them to use current schema rather than compilation
schema (For reference http://www.nabble.com/more-on-system-schema-vs.-user-schema-and-character-constants.-p10885286.html)
With this commit, I am adding an utility method in ValueNode called setCollationUsingCompilationSchema(int)
which will use the compilation schema's collation type for it's DTD. And it will use the passed
int value to set its DTD's collation derivation. This utility method will be used by the subclasses
of ValueNode to set their DTD's collation type to compilation schema's type wherever required.
Note that all the character string types always take their collation from the compilation
schema. For instance, persistent character string type column from a table will take the collation
type from the schema their table belongs to rather than the compilation schema.

I have run the 2 collation related tests, CollationTest and CollationTest2 and they run with
no problems.

> Set correct collation type and derivation on DataTypeDescriptor(DTD).
> ---------------------------------------------------------------------
>                 Key: DERBY-2599
>                 URL: https://issues.apache.org/jira/browse/DERBY-2599
>             Project: Derby
>          Issue Type: New Feature
>          Components: SQL
>    Affects Versions:
>            Reporter: Mamta A. Satoor
>            Assignee: Mamta A. Satoor
>         Attachments: DERBY2599_collationType_default_UCS_BASIC_v1_diff.txt, DERBY2599_collationType_default_UCS_BASIC_v1_stat.txt,
DERBY2599_correct_collation_for_cast_v1_diff.txt, DERBY2599_correct_collation_for_cast_v1_stat.txt,
DERBY2599_getNull_should_set_collation_info_v1_diff.txt, DERBY2599_getNull_should_set_collation_info_v1_stat.txt,
DERBY2599_IntermediatePatch_v1_diff.txt, DERBY2599_IntermediatePatch_v1_stat.txt, DERBY2599_Set_collation_for_aggregates_v1_diff.txt,
DERBY2599_Set_collation_for_aggregates_v1_stat.txt, DERBY2599_Set_collation_for_aggregates_v1_stat.txt,
DERBY2599_Set_collation_for_Max_Min_v1_diff.txt, DERBY2599_set_correct_collation_for_params_and_string_functions_v1_diff.txt,
DERBY2599_set_correct_collation_for_params_and_string_functions_v1_stat.txt, DERBY2599_Use_collation_of_compilation_schema_and_not_current_schema_diff_v1.txt,
> DTD has TypeDescriptorImpl in it which has 2 new fields, namely, collationType and collationDerivation.
These 2 fields are available for all different types of DTDs but only apply to character types.
The other datatypes should ignore these 2 fields.
> This Jira is a placeholder for loading the correct values into collationType and collationDerivation.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message