[
https://issues.apache.org/jira/browse/DERBY-2499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487832
]
A B commented on DERBY-2499:
----------------------------
[ pasted from DERBY-47 comment by Laura Stewart ]
In the Tuning Guide, the IN operator is mentioned in the optimization and query
sections, as shown below:
DML statements and performance
Performance and optimization
Index use and access paths
Joins and performance
Derby's cost-based optimization
Locking and performance
Non-cost-based optimizations
Non-cost-based sort avoidance (tuple filtering)
The MIN() and MAX() optimizations
Overriding the default optimizer behavior
Internal language transformations
Predicate transformations
Static IN predicate transformations
Subquery processing and transformations
DISTINCT elimination in IN, ANY, and EXISTS subqueries
IN/ANY subquery transformation
[ end paste ]
Relevant sections should be updated according to the new 10.3 behavior.
> 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
>
> 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.
