Log-In to post
I, Steven Feuerstein, am obsessed with the PL/SQL language. How else to explain my life since 1994: ten books written about the Oracle PL/SQL language, visits to some 20 countries to train developers on how best to utilize PL/SQL, winner of the coveted Oracle Magazine "PL/SQL Developer of the year award" twice, PL/SQL Evangelist for Quest Software and then Dell from January 2001 to February 2014, writing daily quizzes for the PL/SQL Challenge since April 2010, recorded over 27 hours of video training on PL/SQL at the PL/SQL Channel....yes, my friends, this is definitely an obsession.
And you, dear visitor, can benefit from that obsession right here in Toad World, where I have collected together lots of great resources on PL/SQL. Plus, you might even get some answers to burning questions that have troubled readers of my books for years, such as: "How do you pronounce your last name?" Oh, all right. The answer is (drum roll, please):FOYER-STEEN. And "How can I get in touch with Steven?" Just send me an email!
Your book Oracle PL/SQL pocket reference is really nice i have gone through it.We need some more books like this one.
At Tuesday's Power of Names webinar, you asserted that nesting procedures within procedures within procedures (I believe you said even five levels deep) was often useful and briefly showed us some code utilizing this deeply nested structure. I've been mulling it since and still am not sure I see the utility. I'd balance the gain of "complexity hiding" verses the loss of having an uncertain scope in these trees of subprocedures (seems like you could create a real mess referencing blindly up and down the tree). But that being said I was intrigued by your code snippet where it seem like you were referencing multiple levels of the tree via some kind of indices? It came and went. Any chance you could post the snippet or just explain what it was about?