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

Nothing is gained as far as I am concerned. I would prefer using the traditional syntax. I have had to use the ansi syntax to do full outer joins which I agree shouldn't be need but when I write custom etl for my warehouse I tend to run in data structures that require it (read as bad oltp design).

Ken  

-----Original Message-----
From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Wolfgang Breitling
Sent: Wednesday, October 18, 2006 3:15 PM To: ken_rph_at_yahoo.com
Cc: Jacques.Kilchoer_at_quest.com; 'oracle-l' Subject: RE: should one use ANSI join syntax when writing an Oracle application?

Thanks Ken. That is obviously easier than my "solution". But I can't help wondering what is gained by adding "inner join .. on " to the traditional syntax. Everything else seems to be the same.

Quoting Ken Naim <ken_rph_at_yahoo.com>:

> select A.x, B.y, C.z
> from A
> inner join B on ( A.x = B.x )
> inner join C on ( B.x = C.x and A.x = C.x )
>

-- 
regards

Wolfgang Breitling
Oracle 7,8,8i,9i OCP DBA
Centrex Consulting Corporation
www.centrexcc.com

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


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