db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel John Debrunner (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-2793) Ensure LIKE predicate follows correct rules for determing collation
Date Tue, 10 Jul 2007 00:21:04 GMT

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

Daniel John Debrunner commented on DERBY-2793:
----------------------------------------------

I don't understand what was fixed for DERBY-2725 for LIKE. LikeEscapeNode line 342 still has
the incorrect collation determination.

I have no examples in mind for backwards compatibilty issues with UCS_BASIC, just wondering
if it had been thought about ...

> 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
>             Fix For: 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.


Mime
View raw message