You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Knut Anders Hatlen (JIRA)" <ji...@apache.org> on 2009/12/04 11:54:20 UTC
[jira] Updated: (DERBY-824) Enhance logic in PredicateList to use
variant type of expression while determining search clauses or predicates,
instead of using ConstantNode or ParameterNodes directly.
[ https://issues.apache.org/jira/browse/DERBY-824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Knut Anders Hatlen updated DERBY-824:
-------------------------------------
Issue Type: Improvement (was: Sub-task)
Parent: (was: DERBY-808)
> Enhance logic in PredicateList to use variant type of expression while determining search clauses or predicates, instead of using ConstantNode or ParameterNodes directly.
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-824
> URL: https://issues.apache.org/jira/browse/DERBY-824
> Project: Derby
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 10.2.1.6
> Environment: generic
> Reporter: Satheesh Bandaram
> Priority: Minor
>
> Code in PredicateList can be enhanced to use variant type of expressions while determining whether a predicate qualifies to be a search clause or not.
> Currently code checks for ConstantNode or ParameterNode directly. It should also be possible to enhance this logic to cover constant expressions so that predicates like col = upper('ES5') would also be considered as search clauses. For a customer query in question, having col='ES5' in the query completes the query in about 20 seconds, where as col=upper('ES5') runs for a looong time. (more than several hours)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.