Archives
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 more
The execution of non-query DML can cause all sorts of SQL errors. Steven lays out guidelines in DML Handling code.
Read more
What should be in your exception handling section? Things pertaining to exception handling. What shouldn't? Application code. Learn more.
Read more
Oracle APEX sometimes seems endlessly extensible. If you're missing something from the vast array of native, declarative components, you're likely to find it in the form of an Oracle APEX Plug-in. In this post, we curate a list of favourite plugins, as per some of Insum's consultants.
Read more
A developer takes out "insurance" when they write code to "make sure" or "just in case". This can be unnecessary & unproductive. See examples.
Read more
PL/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 more
The Automatic Time Zone setting in APEX presents some significant challenges. Anton adresses the issues by bypassing this feature with an implementation of his own.
Read more
Steven discusses when it makes sense to choose a string-indexed associative array (one of the three types of PL/SQL collections)
Read more
Lazy 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 more
Watch out for always using an IF statement, consider using a CASE expression, in SQL as well as PL/SQL, and then look for opportunities to use CASE statements as well.
Read more