Why did Oracle change outer joins in ORACLE7?

Hello:

Some of my RPT's don't work anymore under ORACLE7, if they happen to use outer joins in selection statements that deal with 'IN' (values_set) or 'OR' (conditions). This surprised me, and fixing the problem will require a less-than-trivial rewrite of the affected reports.

Why would Oracle wish to restrict use of the (+) join operator in this fashion? I wanted to get all my employees, in health-benefit policy number order...whether they had benefits or not. The way I handled this under Oracle V6 was to ask for a benefit(+) in ('DENTAL','VISION',...) and then I would get the information I wanted. Now this is impossible. :-(

---< MAKE MONEY FAST! Contact Dave Rhodes for details. >--- Steve Frampton E-mail: <frampton_at_vicuna.ocunix.on.ca> Received on Fri May 13 1994 - 20:49:07 CEST