Understanding why best practices are important
Becoming a good PL/SQL programmer
Following the code-writing process
Testing your code
Many people believe that being a good PL/SQL programmer means knowing all about the latest features, obscure syntax for commands in the packages, VARRAYs, object collections, and so on. Knowing all these things means that you’re knowledgeable about the PL/SQL language, but it doesn’t make you a good PL/SQL programmer.
Well-written code executes within a reasonable period of time, provides good performance, and is bug-free whenever possible. But even more important, the code is structured in such a way that you can be assured that it does what it is supposed to do, and when modifications are necessary, you can easily see where they are needed. To help you create code that meets these goals, this chapter discusses some important best practices to keep in mind when programming in PL/SQL. These best practices are taken from our experiences in building real systems.