db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Matrigali (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-2710) disable dynamic like optimization for collated databases
Date Mon, 28 May 2007 05:57:15 GMT

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

Mike Matrigali updated DERBY-2710:
----------------------------------


what is the expected result of a LIKE clause with mismatched collations.  So example is wher
c1 like c2.
case 1) c1 is BASIC collation, c2 TERRITORY collation
case 2) c1 is TERRITORY collation, c2 is BASIC collation

should this just behave the same as where c1 = c2 with different collation types, which I
believe just throws an error.

> disable dynamic like optimization for collated databases
> --------------------------------------------------------
>
>                 Key: DERBY-2710
>                 URL: https://issues.apache.org/jira/browse/DERBY-2710
>             Project: Derby
>          Issue Type: Sub-task
>          Components: SQL
>    Affects Versions: 10.3.0.0
>            Reporter: Mike Matrigali
>            Assignee: Mike Matrigali
>
> I think Code needs to be added to opensource/java/engine/org/apache/derby/impl/sql/compile/LikeEscapeOperatorNode.java
> to disable like optimization for databases with non-default collation.  There is left
over code in this routine that says it disables it for national char by adding a cast to one
of the two sides which I assume then stops some other code from considering the 
> optimization.

-- 
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