RE: mix ANSI and Oracle JOINs?
- From: "Kenneth Naim" <kennethnaim@xxxxxxxxx>
- To: <martin.a.berger@xxxxxxxxx>, "'Oracle-L Freelists'" <oracle-l@xxxxxxxxxxxxx>
- Date: Thu, 23 Dec 2010 11:08:14 -0500
Mixing ansi syntax with Oracle join can cause ORA-600's in certain cases.
I've run into these a few times usually with outer join or full outer joins
of inline views using standard joins.
I find the ansi joins to be good for straight forward sql but very difficult
to write complex sql statements, like outer joins with a where clause on the
deficient side, triangle joins (a -> b -> c -> a) which I don't like to use
but rarely are necessary in databases with poor data models especially some
erp products. I also find the ansi syntax difficult to read and format when
inline views are present.
Ken
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx]
On Behalf Of Martin Berger
Sent: Wednesday, December 22, 2010 2:28 AM
To: Oracle-L Freelists
Subject: mix ANSI and Oracle JOINs?
Hi List,
somewhere in the back of my brain I have the ruleset 'do not mix ANSI and
Oracle JOINs within the same SQL'.
As I have no reference for this I'd like to crosscheck such memories from
time to time as a) this memory is quite unstable and b) as Oracle changes,
it should be checked from time to time.
I searched MOS and asked google, but did not find a real reason.
Should I wipe this memory?
Martin--
//www.freelists.org/webpage/oracle-l
--
//www.freelists.org/webpage/oracle-l
Other related posts:
