If you can't always perform automated regression testing, you can build a simple test harness and, as much as possible, make sure your procedures are broken up into units that can be easily tested. See Steven's example.
Read moreThe execution of non-query DML can cause all sorts of SQL errors. Steven lays out guidelines in DML Handling code.
Read moreWhat should be in your exception handling section? Things pertaining to exception handling. What shouldn't? Application code. Learn more.
Read moreA developer takes out "insurance" when they write code to "make sure" or "just in case". This can be unnecessary & unproductive. See examples.
Read morePL/SQL packages are great! But there is one package feature you shouldn’t use: Initialization. Your first inclination should be to avoid it. Steven Feuerstein explains why.
Read moreSteven discusses when it makes sense to choose a string-indexed associative array (one of the three types of PL/SQL collections)
Read moreLazy can be a good developer characteristic or a terrible one depending on how and when applied. Steven and Marlyn look at examples of each.
Read moreI believe that in the years to come, most of the PL/SQL code that will be written, will be written for (and in) APEX applications. I am, therefore, very happy to join the Insum team for the next phase of my Oracle journey - in PL/SQL and APEX!
Read more