db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-2642) Convert lang/dynamicLikeOptimization.sql to JUnit
Date Tue, 15 May 2007 18:12:16 GMT

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

Knut Anders Hatlen commented on DERBY-2642:
-------------------------------------------

The last part of the query plan (truncated in the output above because the test sets maximumdisplaywidth
too low) looks like this:

qualifiers:
Column[0][0] Id: 2
Operator: <
Ordered nulls: false
Unknown return value: true
Negate comparison result: true
Column[0][1] Id: 2
Operator: <
Ordered nulls: false
Unknown return value: false
Negate comparison result: false

I assume this means that the scan has two qualifiers >= (that is, < negated) and <.
Is this what identifies the query plan as optimized for like?

> Convert lang/dynamicLikeOptimization.sql to JUnit
> -------------------------------------------------
>
>                 Key: DERBY-2642
>                 URL: https://issues.apache.org/jira/browse/DERBY-2642
>             Project: Derby
>          Issue Type: Improvement
>          Components: Test
>    Affects Versions: 10.3.0.0
>            Reporter: Knut Anders Hatlen
>            Priority: Minor
>


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