[
https://issues.apache.org/jira/browse/DERBY-2793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mamta A. Satoor updated DERBY-2793:
-----------------------------------
Urgency: Normal
Labels: derby_triage10_10 (was: )
> Ensure LIKE predicate follows correct rules for determing collation
> -------------------------------------------------------------------
>
> Key: DERBY-2793
> URL: https://issues.apache.org/jira/browse/DERBY-2793
> Project: Derby
> Issue Type: Sub-task
> Components: SQL
> Reporter: Daniel John Debrunner
> Assignee: Mamta A. Satoor
> Labels: derby_triage10_10
>
> The current code in LikeEscapeOperatorNode seems to only check that the
> collations are identical. That is not the correct mechanism for determing
> collation which is based upon SQL spec Section 9.13 "Collation determination"
> or item 12 in the DERBY-1478 wiki page.
> http://wiki.apache.org/db-derby/BuiltInLanguageBasedOrderingDERBY-1478
> I think it's also essential that the (somewhat complex) logic to implement
> collation determination is in a single method, not repeated multiple times
> for each collation.
> There is a TODO in LikeEscapeOperatorNode that might be related to this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
