Posted on 10/07/2025 4:01:36 PM PDT by nickcarraway
![]() |
Click here: to donate by Credit Card Or here: to donate by PayPal Or by mail to: Free Republic, LLC - PO Box 9771 - Fresno, CA 93794 Thank you very much and God bless you. |
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
Spoken like a true Federal worker with lifetime tenure, fat pension, and gold-plated healthcare for life.
Well done, sir.
I’m glad I’m retired.
Grace was simply awe-inspiring. She also chose her team well. We get where we are going perched on the shoulders of giants.
I believe it was Grace (or someone on her team) who found a moth on a circuit board causing problems - and originated the term ‘computer bug.’
Disclaimer: Opinions posted on Free Republic are those of the individual posters and do not necessarily represent the opinion of Free Republic or its management. All materials posted herein are protected by copyright law and the exemption for fair use of copyrighted works.