RE: should one use ANSI join syntax when writing an Oracle applic ation?

From: Allen, Brandon <Brandon.Allen_at_OneNeck.com>
Date: Thu, 19 Oct 2006 09:50:16 -0700
Message-ID: <04DDF147ED3A0D42B48A48A18D574C45059E21C7@NT15.oneneck.corp>

I thought Oracle was smart enough to perform transitive closure on its own even if you don't explicitly write it in your SQL, e.g. Metalink #68979.1:

"Transitivity and Transitive Closure

Purpose

This article explains how the Cost Based Optimizer (CBO) generates transitive
predicates to open potential new access methods."

> -----Original Message-----
> From: oracle-l-bounce_at_freelists.org
> [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Baumgartel, Paul
> Wolfgang,
>
> Just to confirm, your point is that adding
> the (logically unnecessary) "and A.x = C.x" provides more
> information that the optimizer can use to choose a more
> efficient access path?
>
>
>
> -----Original Message-----
> From: oracle-l-bounce_at_freelists.org
> [mailto:oracle-l-bounce_at_freelists.org]On Behalf Of Wolfgang Breitling
>
> I need some help here. How do I code a full transitive
> closure join with the new syntax? In the traditional syntax I can say:
>

Privileged/Confidential Information may be contained in this message or attachments hereto. Please advise immediately if you or your employer do not consent to Internet email for messages of this kind. Opinions, conclusions and other information in this message that do not relate to the official business of this company shall be understood as neither given nor endorsed by it.

--
http://www.freelists.org/webpage/oracle-l

Received on Thu Oct 19 2006 - 11:50:16 CDT