Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <1140674720.1206610644781.JavaMail.jira@brutus>
Date: Thu, 27 Mar 2008 02:37:24 -0700 (PDT)
From: "Dyre Tjeldvoll (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Updated: (DERBY-3138) Optimizer error when vtis are invoked
 with correlated references to outer query blocks
In-Reply-To: <14296100.1192818350719.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/DERBY-3138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dyre Tjeldvoll updated DERBY-3138:
----------------------------------

    Fix Version/s: 10.4.0.0

This issue has no fix version, but has been checked in to trunk after the 10.3 branch was cut, and has not been merged to the 10.3 branch (before the last release). 
(Some have been checked into trunk after 10.4 was cut and then merged to 10.4).

> Optimizer error when vtis are invoked with correlated references to outer query blocks
> --------------------------------------------------------------------------------------
>
>                 Key: DERBY-3138
>                 URL: https://issues.apache.org/jira/browse/DERBY-3138
>             Project: Derby
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 10.4.0.0
>            Reporter: Rick Hillegas
>            Assignee: Rick Hillegas
>             Fix For: 10.4.0.0
>
>         Attachments: derby-3138-fix-aa.diff
>
>
> The following query works fine in 10.3, but raises an optimizer error in the mainline:
> select s.schemaname, t.tableName
> from sys.sysschemas s, sys.systables t
> where t.schemaid=s.schemaid
> and exists
> (
>   select vti.*
>   from table( syscs_diag.space_table( s.schemaname, t.tableName ) ) as vti
>   where vti.numfreepages > -1
> )
> ;
> In the mainline, it raises the following error:
> ERROR 42Y69: No valid execution plan was found for this statement. This may have one of two causes: either you specified a hash join strategy when hash join is not allowed (no optimizable equijoin) or you are attempting to join two external virtual tables, each of which references the other, and so the statement cannot be evaluated.  

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.