Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <932485.1155787754882.JavaMail.jira@brutus>
Date: Wed, 16 Aug 2006 21:09:14 -0700 (PDT)
From: "Yip Ng (JIRA)" <derby-dev@db.apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-1681) Regression (wrong results): Join
 predicate can be ignored for left-most child in a chain of nested unions.
In-Reply-To: <23117349.1155333793855.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

    [ http://issues.apache.org/jira/browse/DERBY-1681?page=comments#action_12428568 ] 
            
Yip Ng commented on DERBY-1681:
-------------------------------

I have reviewed the patch and the logic looks reasonable to me.  I think its ready to be committed.  +1


> Regression (wrong results): Join predicate can be ignored for left-most child in a chain of nested unions.
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-1681
>                 URL: http://issues.apache.org/jira/browse/DERBY-1681
>             Project: Derby
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 10.1.3.1, 10.1.3.0, 10.2.0.0
>            Reporter: A B
>         Assigned To: A B
>             Fix For: 10.2.0.0
>
>         Attachments: d1681_test.patch, d1681_v1.patch, DERBY-1681_v1.html
>
>
> If Derby chooses to do a join between two FromTables and the right table is a chain of UNIONs, then the optimizer may choose to push the join predicate (if provided) down into the UNION and to both children of every UNION in the chain.  But if the predicate cannot be pushed to the children of any of the UNIONs (except the top-level one)  the predicate can end up being ignored altogether with respect to that UNION's children.  The result is that query execution can return rows that do not satisfy the predicate.
> This is a regression introduced in 10.1.2.4 and thus it affects 10.1.3 and 10.2.  I came across this while tracing through code for DERBY-1633.

-- 
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