Quite a while ago, I compared Java and PL/SQL to gauge their relative performance.

Recently (okay, back in mid-June) I got this request.

One thing I would like to compare is Java vs PL/SQL using native compilation (search Oracle for NCOMP). Would you be willing to repeat your …

The email from a developer starts with a complaint and moves on to a plea: "I am constantly having to look at "IF o_status = 0". Code would be a lot more compact and easy to read if exceptions were used. Request favor: Please consider blogging about using exception handling vs …

First, the confusion. A couple of comments asked for code, offering to "fix" the problems. Specifically, offering to optimize or improve the PL/SQL. The code was already posted, but I failed to make that clear. Here's a recap of the various blog entries on this subject.

1. PL/SQL vs …

There appear to be four responses. Two were numbered, the third is a rambling thought on scalability, and the fourth is a thought on management's discomfort with the truth.

A stored procedure isn't really very easy to understand. There's a profound fascination with triggers and stored procedures, and they're both really bad ideas. I can't say enough bad things about stored procedures. See PL/SQL vs. Java - Which is REALLY faster? and Over-Solving the Problem or When your architect …