Re: Oracle outer join syntax (+) not working???

On Sat, 17 Jun 2006, damorgan@xxxxxxxxx wrote:
Galen Boyer wrote:
On 17 Jun 2006, REMOVE_BEFORE_REPLYING_dportas@xxxxxxx wrote:

What suprises me is that Oracle's (+) syntax still seems to be
common. Given the important advantages of the standard syntax (full
joins; non-equijoins; well-defined evaluation order; portability)
it's odd that it doesn't seem to have gained the universal
acceptance in the Oracle world the way it has done elsewhere.

Once I found out that FULL outer join is supported but a full
outer join
isn't supported with the (+) syntax, I switched to INNER JOIN,
LEFT/RIGHT/FULL OUTER JOIN syntax. Haven't looked back.

Many of us have been doing full out joins in the standard Oracle
syntax for years such as the following:

select * from (
select v.vessel_id
from vessels v, trips t
where v.vessel_id = t.vessel_id(+)
union
select t.vessel_id
from vessels v, trips t
where v.vessel_id(+) = t.vessel_id);

Not as pretty but certainly easy.

Unions are for sissys...

--
Galen Boyer
.

Relevant Pages

  • Re: CROSS JOIN
    ... > was that depreciating the original FROM .. ... WHERE syntax would never ... > The problem is that the WHERE clause is done after the FROM clause. ... but thats just outer join stuff. ...
    (comp.databases)
  • Re: Difference in Left Join, Right Join
    ... RIGHT syntax exist. ... If you write SQL such that what you feel is the driving table is at ... The above is Oracle outer join syntax, ...
    (comp.databases.oracle.misc)
  • Re: SQLServer/Oracle Views
    ... >Mike John ... I suddenly remembered something Joe Celko ... It's not a syntax difference of the old outer-join syntax, ... LEFT OUTER JOIN TableB AS b ...
    (microsoft.public.sqlserver.programming)
  • Re: CROSS JOIN
    ... WHERE syntax would never ... FROM Foo LEFT OUTER JOIN Bar ON a = 42 ... FROM Foo, Bar, Gulk ... You can see the "between-ness" relationship. ...
    (comp.databases)
  • Re: Not Common both Tables
    ... For exemple, I'm sure that the Full Outer Join is not available under ... I'm pretty sure that the Exitsstatement and the UNION ... For the syntax error, it's probably a missing AND in the first subquery of ... You can also use an Outer Join and select all the records which will have ...
    (microsoft.public.access.adp.sqlserver)