[
https://issues.apache.org/jira/browse/DERBY-2499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12490447
]
A B commented on DERBY-2499:
----------------------------
> Is this part sitll the JDBC perspective? It looks like straight SQL to me...
You're correct, the sentence "Another way to capture this logic..." is meant to
demonstrate the probe predicate functionality in a SQL-equivalent (as opposed
to a JDBC-equivalent) way. So no, that sentence (and the subsequent query) is
not part of the JDBC "perspective"...
> 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.
