[
https://issues.apache.org/jira/browse/DERBY-2876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mamta A. Satoor closed DERBY-2876.
----------------------------------
Resolution: Duplicate
I am closing this jira entry because it is a subtask of DERBY-1478. I have
opened DERBY-3651 as a standalone task to finish the rest of the work which was
going to go as part of this subtask.
> Ensure the DataTypeDescriptor.comparable() implements the correct rules for
> determing the collation to use.
> -----------------------------------------------------------------------------------------------------------
>
> Key: DERBY-2876
> URL: https://issues.apache.org/jira/browse/DERBY-2876
> Project: Derby
> Issue Type: Sub-task
> Components: SQL
> Affects Versions: 10.3.1.4, 10.4.1.3
> Reporter: Daniel John Debrunner
>
> The current implementation of comparable requires that collation type *and*
> derivation must match for the types to be comparable.
> This is not correct according to SQL Standard 9.13, e.g. with non-matching
> types and one derivation of implicit and one of none, then the types are
> comparable.
> Possibly this method is not the correct location for this functionality, as
> no indication can be given of the correct collation to use, just if they are
> comparable or not.
> Would be fixed by a correct implementation of the 9.13 rules under
> DERBY-2875, but that's marked as an improvement.
> This issue is to record the fact that the comparision logic is currently
> incorrect and so DERBY-1478 is not yet complete.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
