[DERBY-2599] Set correct collation type and derivation on DataTypeDescriptor(DTD).

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.3.1.4
• Fix Version/s: 10.3.1.4
• Component/s: SQL
• Assignee: Mamta A. Satoor
• Reporter: Mamta A. Satoor
• Created: 30/Apr/07 17:31
• Updated: 02/May/13 02:29
• Resolved: 03/Jul/07 16:41

Description

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.

Issue Links

• incorporates: DERBY-2776 Internally generated CAST nodes should not use the collation of the current compilation schema. Instead they should use collation of target type passed to it.
• incorporates: DERBY-2777 Parameters should take their collation from the context in which they are getting used rather than the current compilation schema
• incorporates: DERBY-2722 Set correct collation type and derivation for result character string types from CHAR, VARCHAR and XMLSERIALIZE functions
• incorporates: DERBY-2723 Set correct collation type and derivation for result from user defined functions' that return character string type.
• incorporates: DERBY-2724 Set correct collation type and derivation for result character string types from CURRENT ISOLATION, CURRENT_USER, SESSION_USER, SYSTEM_USER, CURRENT SCHEMA and CURRENT SQLID.
• incorporates: DERBY-2731 String literal constants currently take the collation of the compilation schema but the wiki page http://wiki.apache.org/db-derby/BuiltInLanguageBasedOrderingDERBY-1478 expects USER schema collation.
• is depended upon by: DERBY-2335 Compare character datatypes with different collation ordering.
• is related to: DERBY-2668 At the time of compilation of a comparison operation, if the collation types of the operands do not match, then we should throw a meaningful error message.