PL/SQL is a procedural language designed specifically to embrace SQL statements within its syntax. PL/SQL program units are compiled by the Oracle Database server and stored inside the database. And at run-time, both PL/SQL and SQL run within the same server process, bringing optimal efficiency. PL/SQL automatically inherits the robustness, security, and portability of the Oracle Database.
An application that uses Oracle Database is worthless unless only correct and complete data is persisted. The time-honored way to ensure this is to expose the database only via an interface that hides the implementation details—the tables and the SQL statements that operate on these. This approach is generally called the smart database or SmartDB paradigm, because PL/SQL subprograms inside the database issue the SQL statements from code that implements the surrounding business logic; and because the data can be changed and viewed only through a PL/SQL interface.
Bryn Llewellyn (@BrynLite, Blog) is the Product Manager for PL/SQL and edition-based redefinition. He is a member of the team of engineers who are responsible for the implementation of these capabilities inside Oracle Database. He acts as the two-way conduit between these engineers and developers who use Oracle Database, write PL/SQL code, and use EBR. He listens to requests for enhancements and he writes about, and talks about, new features and enhancements.
Steven Feuerstein (@sfonplsql, Blog) leads Oracle's team of Developer Advocates and his special interest within the team is PL/SQL. He writes a PL/SQL column in Oracle Magazine and has created the Practically Perfect PL/SQL series YouTube Channel.
Both Bryn and Steven present regularly at Oracle User Group conferences.
Getting Rid of Hard-Coding in PL/SQL
This first playlist of P3 explores the various forms of hard-coding that can appear in PL/SQL, and how best to get rid of them.