Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Sat, 29 Sep 2012 05:33:07 +1100 (NCT)
From: "Mamta A. Satoor (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: <2071850674.140435.1348857187813.JavaMail.jiratomcat@arcas>
Subject: [jira] [Updated] (DERBY-4742) Make outer join reordering work for
 right outer joins
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Mamta A. Satoor updated DERBY-4742:
-----------------------------------

    Urgency: Normal
     Labels: derby_triage10_10  (was: )
    
> Make outer join reordering work for right outer joins
> -----------------------------------------------------
>
>                 Key: DERBY-4742
>                 URL: https://issues.apache.org/jira/browse/DERBY-4742
>             Project: Derby
>          Issue Type: Improvement
>          Components: SQL
>    Affects Versions: 10.0.2.0, 10.0.2.1, 10.1.1.0, 10.1.2.1, 10.1.3.1, 10.2.1.6, 10.2.2.0, 10.3.1.4, 10.3.2.1, 10.3.3.0, 10.4.1.3, 10.4.2.0, 10.5.1.1, 10.5.2.0, 10.5.3.0, 10.6.1.0
>            Reporter: Dag H. Wanvik
>              Labels: derby_triage10_10
>
> Currently, Derby only attempts to reorder (into left deep) left outer join queries. Right outer join queries are commented out, apparently due to implementation difficulties, cf. this comment in HalfOuterJoinNode.LOJ_reorderable.
> // It is much easier to do LOJ reordering if there is no ROJ.
> // However, we ran into some problem downstream when we transform an ROJ
> // into LOJ -- transformOuterJoin() didn't expect ROJ to be transformed
> // into LOJ alread.  So, we skip optimizing ROJ at the moment.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira