I checked out when 3 or 4 guys asked me how I could produce a query, based upon part no. that had 2 tables which had, a master file table mind you, which had different attributes of the same component. Is that an inner our outer table join?
oh hai there, Little Bobby Tables :)
At work many (many) years ago (ca. Oracle 6), I got into an argument with a DBA who was looking at my SQL code. I coded a correlated subquery for a table that contained values that I wanted to exclude from my set. I had a "not in (select... from a.table 1...) and he said you don't us NOT in a subselect. I said of course not, but this is not a subselect, it's a correlated subquery and NOT is just fine.
He didn't get it. He refused to believe me that NOT was okay.
Back then, nobody was using correlated subqueries because it was too complicated for the average programmer to understand, but the explains were very efficient. I woulld nest them two or three deep, because they're great at index retrievals without returning row data. The system I built was eventually sold to Price Waterhouse by the business side of the project, and years later I saw correlated subqueries everywhere in their code.
-PJ