[
https://issues.apache.org/jira/browse/DERBY-2599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mamta A. Satoor updated DERBY-2599:
-----------------------------------
Attachment: DERBY2599_Set_collation_for_aggregates_v1_stat.txt
DERBY2599_Set_collation_for_aggregates_v1_diff.txt
Attaching patch DERBY2599_Set_collation_for_aggregates_v1_diff.txt which does
the job of setting the correct collation type and derivation for aggregates. As
per SQL standard, if the operands of the aggregate methods are string operands
and they do not all have the same collation derivaiton and type on them, then
the resultant string operand will have collation derivaiton of NONE. One thing
that is missing is as per SQL spec, in a comparison operator, as far as there
is one operand with non-NONE collation derivation, the comparison should work.
I do not have that part working yet. If the two operands of the comparison
operator do not have the same collation, the comparison will fail. Also, if
both the sides of the comparison operator have NONE collation, the current
DERBY10.3 code will not catch that. Both of these issues can go as a subsequent
patch.
The aggregate methods that are covered by the patch are COALESCE, CONCATENATE,
NULLIF, CASE
> 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: 10.3.0.0
> Reporter: Mamta A. Satoor
> Assigned To: 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_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
>
>
> 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.
