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 "Satheesh Bandaram (JIRA)" <de...@db.apache.org> on 2006/01/18 20:38:42 UTC
[jira] Created: (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.
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: http://issues.apache.org/jira/browse/DERBY-824
Project: Derby
Type: Sub-task
Versions: 10.2.0.0
Environment: generic
Reporter: Satheesh Bandaram
Priority: Minor
Fix For: 10.2.0.0
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.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[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.
Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
[ 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.
[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.
Posted by "Kathey Marsden (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-824?page=all ]
Kathey Marsden updated DERBY-824:
---------------------------------
Fix Version/s: (was: 10.2.0.0)
removing from 10.2. see:
http://www.nabble.com/10.2-High-Value-Fix-Candidates-and-Fix-Version-Adjustments-tf2007999.html
> 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: http://issues.apache.org/jira/browse/DERBY-824
> Project: Derby
> Issue Type: Sub-task
> Components: SQL
> Affects Versions: 10.2.0.0
> 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.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[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.
Posted by "Mike Matrigali (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-824?page=all ]
Mike Matrigali updated DERBY-824:
---------------------------------
Component: SQL
> 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: http://issues.apache.org/jira/browse/DERBY-824
> Project: Derby
> Type: Sub-task
> Components: SQL
> Versions: 10.2.0.0
> Environment: generic
> Reporter: Satheesh Bandaram
> Priority: Minor
> Fix For: 10.2.0.0
>
> 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.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (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.
Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12785867#action_12785867 ]
Knut Anders Hatlen commented on DERBY-824:
------------------------------------------
I converted this sub-task to a top-level issue since its parent (DERBY-808) was closed.
> 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.
[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.
Posted by "Rick Hillegas (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-824?page=all ]
Rick Hillegas updated DERBY-824:
--------------------------------
Urgency: Low
> 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: http://issues.apache.org/jira/browse/DERBY-824
> Project: Derby
> Issue Type: Sub-task
> Components: SQL
> Affects Versions: 10.2.0.0
> Environment: generic
> Reporter: Satheesh Bandaram
> Priority: Minor
> Fix For: 10.2.0.0
>
>
> 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.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira