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 "Andrew McIntyre (JIRA)" <de...@db.apache.org> on 2006/04/24 22:36:37 UTC
[jira] Reopened: (DERBY-808) PreparedStatements can take longer to
execute than equivalent Statements when there are multiple join conditions
mixed with some search clauses.
[ http://issues.apache.org/jira/browse/DERBY-808?page=all ]
Andrew McIntyre reopened DERBY-808:
-----------------------------------
> PreparedStatements can take longer to execute than equivalent Statements when there are multiple join conditions mixed with some search clauses.
> ------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-808
> URL: http://issues.apache.org/jira/browse/DERBY-808
> Project: Derby
> Type: Bug
> Components: SQL
> Versions: 10.1.2.0, 10.2.0.0
> Environment: generic
> Reporter: Satheesh Bandaram
> Assignee: Satheesh Bandaram
> Fix For: 10.2.0.0, 10.1.3.0, 10.1.2.2
> Attachments: DERBY-808.patch
>
> PreparedStatements could take much longer than Statements because of incorrect search clause transitive closure optimization. For the customer case I investigated this problem, Statement would complete in about 13 seconds, where as equivalent PreparedStatement ran "forever". (stoped it after hours)
> I think there a problem with PredicateList.searchClauseTransitiveClosure method. This method tries to add new search clauses based on equality join between tables involved. Current code only looks for ConstantNodes on the right side of searchClauses. This would miss ParameterNodes, so Derby might miss search clause transitive closure optimizations for PreparedStatements.
--
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