What is the place of a record-oriented procedural language in the relational world?
Its place is proven: SQL is not a complete language. Some people can perform seeming miracles with straight SQL, but the statements can end up looking like pretzels created by someone who is experimenting with hallucinogens. Some people can perform seeming miracles with straight SQL, but the statements can end up looking like pretzels created by someone who is experimenting with hallucinogens. We need more than SQL to build our applications, whether it is the implementation of business rules or application logic. PL/SQL remains the fastest and easiest way to access and manipulate data in an Oracle RDBMS, and I am certain it is going to stay that way for decades. Some might worry that using PL/SQL would chain them to Oracle and restrict their future options. What would you say to those you who wish to create database-agnostic applications? Well, like I said earlier, PL/SQL is all I know, so I automatically self-select into working with and talking to people who have committed to both Or