Archives

In this blog, Steven proposes a refactoring exercise. Look at the code. What changes does it need? Discuss it with him on Feuertips June 16.

In this blog for episode 12 of Feuertips, Steve shows us how to suppress row-level errors in Oracle Database.

Naming conventions are key to writing high-quality code. Steven explores what motivates conventions to clarify what works best for us and why.

In this episode: to manipulate in-program data in set-kinda ways, use nested tables. They have cool, set-oriented features.

The WITH keyword lets us use modular design with SQL and helps avoid redundant logic in SQL statements. Learn more in this Feuertips episoide

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.

The execution of non-query DML can cause all sorts of SQL errors. Steven lays out guidelines in DML Handling code.

What should be in your exception handling section? Things pertaining to exception handling. What shouldn't? Application code. Learn more.

A developer takes out "insurance" when they write code to "make sure" or "just in case". This can be unnecessary & unproductive. See examples.

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.