[jira] Resolved: (DERBY-2793) Ensure LIKE predicate follows correct rules for determing collation

["Mamta A. Satoor (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/DERBY-2793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mamta A. Satoor resolved DERBY-2793.
------------------------------------

       Resolution: Fixed
    Fix Version/s: 10.4.0.0
                   10.3.1.1

Merged the change from main codeline (revision 553395) into 10.3.1.1 codeline (revision 553399).

> 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
>             Fix For: 10.3.1.1, 10.4.0.0
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.