Common Mistakes in Oracle PL/SQL Programming

You did WHAT? You wrote an explicit cursor? You declared a variable using the VARCHAR2 datatype? You raised an exception to skip over unnecessary lines of code? If slip-ups like these sound familiar (or if you don’t know why these are mistakes), join Quest for a one-hour Webcast featuring guest speaker, Steven Feuerstein, as he examines common mistakes in Oracle PL/SQL programming. Learn how to correct mistakes to improve the maintainability and performance of your application. This Webcast will also demonstrate codexpert — a powerful feature available within Toad® that will help you avoid common mistakes and ensure you implement PL/SQL best practices in your daily activities. About the Guest Speaker: Steven Feuerstein is considered one of the world’s leading experts on the Oracle PL/SQL language, having written nine published books on PL/SQL (all from O’Reilly & Associates). Steven has been developing software since 1980, spent five years with Oracle (1987-1992) and serves as a Senior Technology Advisor to Quest Software.

15 thoughts on “Common Mistakes in Oracle PL/SQL Programming”

  1. Coming from using sql*plus in cost systems professionally until 1994, then vanishing into mechanical engineering until right now, this is almost understandable.

  2. If you don’t care anything about performace then sure put your data logic in PL/SQL. While you code is still chunking along my pure sql statements will be long over and done with.
    Go read Ask Tom on this topic before giving the world horrible advice.

  3. PL/SQL is great and completely under-used. SQL by itself is a nightmare. Why would anyone want to write the entire logic of a program in a single sentence? Complicated SQL statments are nearly impossible to write, read, modify, or debug. A bit of logic written programmatically in PL/SQL (or equivalent procedural language) is clear and simple.

Leave a Comment