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

>But on the other hand, from my experience, application performance always prevails code clarity requirements.
Oh yes, but on the other hand Oracle bug free code prevails over all the rest :-) I mean I was told that on 9i someone hit ANSI join syntax bug. Let's hope it was a unique case and Oracle already fixed it. But otherwise yes - if used *properly* ANSI syntax may be more readable.

It's only that ANSI comitee forgot to include special alter session flags: Disable "select *(star) from"
Disable "natural join"
And may be a few more default runtime behaviours should be disabled. And yes, those flags should be disabled by default of course.

-----Original Message-----
From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Mindaugas Navickas Sent: 18. október 2006 14:20
To: mwf_at_rsiz.com; breitliw_at_centrexcc.com; 'oracle-l' Cc: 'Mladen Gogala'; niall.litchfield_at_gmail.com Subject: RE: should one use ANSI join syntax when writing an Oracle application?

"My guess is that it would not be too hard to do a non-outer equijoin and slap that together with the pair of not-in or minuses and thereby compete with ANSI's cost."

Anybody volunteer to try it with purpose to show how "clear" statement would become?

In my previous e-mail I also wanted to stress clarity of the construct when using ANSI full outer join - to argue statements made by other listers. But on the other hand, from my experience, application performance always prevails code clarity requirements. And because of this I am not ready making my live harder to find "Oracle native way" when ANSI syntax is available which preserves both clarity and performance. Hopefully, Mladen will not be the one who reviews my code :-)

Mindaugas

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


Fyrirvari/Disclaimer
http://www.landsbanki.is/disclaimer
--
http://www.freelists.org/webpage/oracle-l