db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "A B (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-2499) Update Tuning Guide documentation to reflect the new static IN list transformation that occurs as a result of DERBY-47.
Date Wed, 25 Apr 2007 16:57:15 GMT

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

A B commented on DERBY-2499:
----------------------------

+1 to commit, Laura.

If you're so inclined you could probably delete the following sentence, as I'm starting to
think it's more confusing than useful:

   The probe predicate orig_airport = ? might appear like an equality comparison to a single
   value specified by the user, but it is not an equality comparison.

If you choose to do so you can just make that change before your commit; no need to review
it again if that's all that changes.

Thanks for your help on this.

> Update Tuning Guide documentation to reflect the new static IN list transformation that
occurs as a result of DERBY-47.
> -----------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-2499
>                 URL: https://issues.apache.org/jira/browse/DERBY-2499
>             Project: Derby
>          Issue Type: Sub-task
>          Components: Documentation
>    Affects Versions: 10.3.0.0
>            Reporter: A B
>         Assigned To: Laura Stewart
>            Priority: Minor
>         Attachments: derby2499_1.diff, derby2499_2.diff, derby2499_3.diff, rtuntransform582.html,
rtuntransform582.html, rtuntransform582.html
>
>
> DERBY-47 changed the static rewrite logic for IN lists.  Whereas we used to create a
BETWEEN predicate for IN-lists that contain all constants and then use that predicate to limit
the scan, we now create a "probe predicate" for IN-lists that contain all constants *and/or*
parameter nodes and then use that new predicate to perform execution-time probing.
> The documentation in the Tuning Guide needs to be updated to reflect this change in behavior.

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