|Oracle® Database Development Guide
12c Release 1 (12.1)
|PDF · Mobi · ePub|
This chapter introduces the advanced PL/SQL features and refers to other chapters or documents for more information.
The PL/SQL data types include the SQL data types, additional scalar data types, and composite data types. You define the composite data types. You can also define subtypes of the scalar data types. For more information, see Section 11.4.4, "PL/SQL Data Types."
Dynamic SQL is a programming methodology for generating and running SQL statements at runtime. It is useful when writing general-purpose and flexible programs like dynamic query systems, when writing programs that must run database definition language (DDL) statements, or when you do not know at compile time the full text of a SQL statement or the number or data types of its input and output variables. For more information, see Section 11.4.9, "PL/SQL Dynamic SQL."
The PL/SQL optimize level determines how much the PL/SQL optimizer can rearrange code for better performance. This level is set with the compilation parameter
PLSQL_OPTIMIZE_LEVEL, which is described in Oracle Database Reference. For more information, see Section 11.3.1, "PLSQL_OPTIMIZE_LEVEL Compilation Parameter."
You can usually speed up PL/SQL units by compiling them into native code (processor-dependent system code), which is stored in the SYSTEM tablespace. For more information about compiling PL/SQL units for native execution, see Section 11.7, "Compiling PL/SQL Units for Native Execution."
Exceptions (PL/SQL runtime errors) can arise from design faults, coding mistakes, hardware failures, and many other sources. You cannot anticipate all possible exceptions, but you can write exception handlers that let your program to continue to operate in their presence. For more information, see Oracle Database PL/SQL Language Reference.
Use new features with the latest database release and disable them when running the application in an older database release.
Activate debugging or tracing statements in the development environment and hide them when running the application at a production site.
Oracle recommends against using conditional compilation to change the attribute structure of a type, which can cause dependent objects to "go out of sync" or dependent tables to become inaccessible.
To change the attribute structure of a type, Oracle recommends using the
TYPE statement (described in Oracle Database SQL Language Reference), which propagates changes to dependent objects.
Conditional compilation is subject to restrictions.
For more information about conditional compilation, see Oracle Database PL/SQL Language Reference.
Bulk binding minimizes the performance overhead of the communication between PL/SQL and SQL, which can greatly improve performance. For more information, see Section 11.4.8, "Overview of Bulk Binding."