Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <63060439.1137611204829.JavaMail.jira@ajax.apache.org>
Date: Wed, 18 Jan 2006 20:06:44 +0100 (CET)
From: "Satheesh Bandaram (JIRA)" <derby-dev@db.apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Resolved: (DERBY-808) PreparedStatements can take longer to
 execute than Statements. There seem to be a problem with
 searchClauseTransitiveClosure method in PredicateList.java
In-Reply-To: <1774083642.1137029900284.JavaMail.jira@ajax.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/DERBY-808?page=all ]
     
Satheesh Bandaram resolved DERBY-808:
-------------------------------------

    Fix Version: 10.1.2.2
     Resolution: Fixed

Fix has been submitted to trunk and 10.1 branches.

> PreparedStatements can take longer to execute than Statements. There seem to be a problem with searchClauseTransitiveClosure method in PredicateList.java
> ---------------------------------------------------------------------------------------------------------------------------------------------------------
>
>          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
>      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