1 / 39

Creating Packages

Creating Packages. Objectives. After completing this lesson, you should be able to do the following: Describe packages and list their components Create a package to group together related variables, cursors, constants, exceptions, procedures, and functions

rgriffin
Download Presentation

Creating Packages

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Creating Packages

  2. Objectives • After completing this lesson, you should be able to do the following: • Describe packages and list their components • Create a package to group together related variables, cursors, constants, exceptions, procedures, and functions • Designate a package construct as either public or private • Invoke a package construct • Describe the use of a bodiless package

  3. Lesson Agenda • Identifying the benefits and the components of packages • Working with packages: • Creating the package specification and body • Invoking the package subprograms • Removing a package • Displaying the package information

  4. What Are PL/SQL Packages? • A package is a schema object that groups logically related PL/SQL types, variables, and subprograms. • Packages usually have two parts: • A specification (spec) • A body • The specification is the interface to the package. It declares the types, variables, constants, exceptions, cursors, and subprograms that can be referenced from outside the package. • The body defines the queries for the cursors and the code for the subprograms. • Enable the Oracle server to read multiple objects into memory at once.

  5. Advantages of Using Packages • Modularity: Encapsulating related constructs • Easier maintenance: Keeping logically related functionality together • Easier application design: Coding and compiling the specification and body separately • Hiding information: • Only the declarations in the package specification are visible and accessible to applications • Private constructs in the package body are hidden and inaccessible • All coding is hidden in the package body

  6. Advantages of Using Packages • Added functionality: Persistency of public variables and cursors • Better performance: • The entire package is loaded into memory when the package is first referenced. • There is only one copy in memory for all users. • The dependency hierarchy is simplified. • Overloading: Multiple subprograms of the same name

  7. Components of a PL/SQL Package Package specification variable Public Procedure A declaration; variable Procedure B definition … Procedure A definition BEGIN … END; Private variable Package body

  8. The Visibility of a Package’s Components Package specification public_var Procedure A; External code private_var Procedure B ISBEGIN … END; Procedure A IS BEGIN … END; local_var Package body

  9. Developing PL/SQL Packages: Overview View errors/warnings in SQL Developer YES Use SHOW ERRORScommand in SQL*Plus Create/edit package body and spec Compilerwarnings/errors? View compilerwarnings/errors NO Use USER/ALL/DBA_ERRORS views Invoke package subprograms

  10. Lesson Agenda • Identifying the benefits and the components of packages • Working with packages: • Creating the package specification and body • Invoking the package subprograms • Removing a package • Displaying the package information

  11. Creating the Package Specification:Using the CREATE PACKAGE Statement • The ORREPLACE option drops and re-creates the package specification. • Variables declared in the package specification are initialized to NULL by default. • All the constructs declared in a package specification are visible to users who are granted privileges on the package. CREATE [OR REPLACE] PACKAGE package_name IS|AS public type and variable declarations subprogram specifications END [package_name];

  12. Creating the Package Specification:Using SQL Developer 4 3 1 2 5

  13. Creating the Package Body:Using SQL Developer 4 1 2 3 5

  14. Example of a Package Specification: comm_pkg • V_STD_COMM is a public global variable initialized to 0.10. • RESET_COMM is a public procedure used to reset the standard commission based on some business rules. It is implemented in the package body. -- The package spec with a public variable and a -- public procedure that are accessible from -- outside the package. CREATE OR REPLACE PACKAGE comm_pkg IS v_std_comm NUMBER := 0.10; --initialized to 0.10 PROCEDURE reset_comm(p_new_comm NUMBER); END comm_pkg; /

  15. Creating the Package Body • The ORREPLACE option drops and re-creates the package body. • Identifiers defined in the package body are private and not visible outside the package body. • All private constructs must be declared before they are referenced. • Public constructs are visible to the package body. CREATE [OR REPLACE] PACKAGE BODY package_name IS|AS private type and variable declarations subprogram bodies [BEGIN initialization statements] END [package_name];

  16. Example of a Package Body: comm_pkg CREATE OR REPLACE PACKAGE BODY comm_pkg IS FUNCTION validate(p_comm NUMBER) RETURN BOOLEAN IS v_max_comm employees.commission_pct%type; BEGIN SELECT MAX(commission_pct) INTO v_max_comm FROM employees; RETURN (p_comm BETWEEN 0.0 AND v_max_comm); END validate; PROCEDURE reset_comm (p_new_comm NUMBER) IS BEGIN IF validate(p_new_comm) THEN v_std_comm := p_new_comm; -- reset public var ELSE RAISE_APPLICATION_ERROR( -20210, 'Bad Commission'); END IF; END reset_comm; END comm_pkg;

  17. Invoking the Package Subprograms: Examples -- Invoke a function within the same packages: CREATE OR REPLACE PACKAGE BODY comm_pkg IS ... PROCEDURE reset_comm(p_new_comm NUMBER) IS BEGIN IF validate(p_new_comm) THEN v_std_comm := p_new_comm; ELSE ... END IF; END reset_comm; END comm_pkg; -- Invoke a package procedure from SQL*Plus: EXECUTE comm_pkg.reset_comm(0.15) -- Invoke a package procedure in a different schema: EXECUTE scott.comm_pkg.reset_comm(0.15)

  18. Invoking the Package Subprograms: Using SQL Developer

  19. Creating and Using Bodiless Packages CREATE OR REPLACE PACKAGE global_consts IS c_mile_2_kilo CONSTANT NUMBER := 1.6093; c_kilo_2_mile CONSTANT NUMBER := 0.6214; c_yard_2_meter CONSTANT NUMBER := 0.9144; c_meter_2_yard CONSTANT NUMBER := 1.0936; END global_consts; BEGIN DBMS_OUTPUT.PUT_LINE('20 miles = ' || 20 * global_consts.c_mile_2_kilo || ' km'); END; CREATE FUNCTION mtr2yrd(p_m NUMBER) RETURN NUMBER IS BEGIN RETURN (p_m * global_consts.c_meter_2_yard); END mtr2yrd; / EXECUTE DBMS_OUTPUT.PUT_LINE(mtr2yrd(1))

  20. Removing Packages: Using SQL Developer or the SQL DROP Statement Drop package specification and body Drop package body only -- Remove the package specification and body DROP PACKAGE package_name; -- Remove the package body only DROP PACKAGE BODY package_name;

  21. Working with Packages

  22. Objectives • After completing this lesson, you should be able to do the following: • Overload package procedures and functions • Use forward declarations • Create an initialization block in a package body • Manage persistent package data states for the life of a session • Use PL/SQL tables and records in packages

  23. Lesson Agenda • Overloading package subprograms, using forward declarations, and creating an initialization block in a package body • Managing persistent package data states for the life of a session and using PL/SQL tables and records in packages

  24. Overloading Subprograms in PL/SQL • Enables you to create two or more subprograms with the same name • Requires that the subprogram’s formal parameters differ in number, order, or data type family • Enables you to build flexible ways for invoking subprograms with different data • Provides a way to extend functionality without loss of existing code; that is, adding new parameters to existing subprograms • Provides a way to overload local subprograms, package subprograms, and type methods, but not stand-alone subprograms

  25. Overloading Procedures Example:Creating the Package Specification CREATE OR REPLACE PACKAGE dept_pkg IS PROCEDURE add_department(p_deptno departments.department_id%TYPE, p_name departments.department_name%TYPE :='unknown', p_loc departments.location_id%TYPE := 1700); PROCEDURE add_department (p_name departments.department_name%TYPE := 'unknown', p_loc departments.location_id%TYPE := 1700); END dept_pkg; /

  26. Overloading Procedures Example:Creating the Package Body CREATE OR REPLACE PACKAGE BODY dept_pkg IS PROCEDURE add_department –- First procedure’s declaration (p_deptno departments.department_id%TYPE, p_name departments.department_name%TYPE := 'unknown', p_loc departments.location_id%TYPE := 1700) IS BEGIN INSERT INTO departments(department_id, department_name, location_id) VALUES (p_deptno, p_name, p_loc); END add_department; PROCEDURE add_department –- Second procedure’s declaration (p_name departments.department_name%TYPE := 'unknown', p_loc departments.location_id%TYPE := 1700) IS BEGIN INSERT INTO departments (department_id, department_name, location_id) VALUES (departments_seq.NEXTVAL, p_name, p_loc); END add_department; END dept_pkg; /

  27. Overloading and the STANDARD Package • A package named STANDARD defines the PL/SQL environment and built-in functions. • Most built-in functions are overloaded. An example is the TO_CHAR function: • A PL/SQL subprogram with the same name as a built-in subprogram overrides the standard declaration in the local context, unless qualified by the package name. FUNCTION TO_CHAR (p1 DATE) RETURN VARCHAR2; FUNCTION TO_CHAR (p2 NUMBER) RETURN VARCHAR2; FUNCTION TO_CHAR (p1 DATE, P2 VARCHAR2) RETURN VARCHAR2; FUNCTION TO_CHAR (p1 NUMBER, P2 VARCHAR2) RETURN VARCHAR2; . . .

  28. Illegal Procedure Reference • Block-structured languages such as PL/SQL must declare identifiers before referencing them. • Example of a referencing problem: CREATE OR REPLACE PACKAGE BODY forward_pkg IS PROCEDURE award_bonus(. . .) IS BEGIN calc_rating (. . .); --illegal reference END; PROCEDURE calc_rating (. . .) IS BEGIN ... END; END forward_pkg; /

  29. Using Forward Declarations toSolve Illegal Procedure Reference • In the package body, a forward declaration is a private subprogram specification terminated by a semicolon. CREATE OR REPLACE PACKAGE BODY forward_pkg IS PROCEDURE calc_rating (...);-- forward declaration -- Subprograms defined in alphabetical order PROCEDURE award_bonus(...) IS BEGIN calc_rating (...); -- reference resolved! . . . END; PROCEDURE calc_rating (...) IS -- implementation BEGIN . . . END; END forward_pkg;

  30. Initializing Packages • The block at the end of the package body executes once and is used to initialize public and private package variables. CREATE OR REPLACE PACKAGE taxes IS v_tax NUMBER; ... -- declare all public procedures/functions END taxes; / CREATE OR REPLACE PACKAGE BODY taxes IS ... -- declare all private variables ... -- define public/private procedures/functions BEGIN SELECT rate_value INTO v_tax FROM tax_rates WHERE rate_name = 'TAX'; END taxes; /

  31. Using Package Functions in SQL • You use package functions in SQL statements. • To execute a SQL statement that calls a member function, the Oracle database must know the function’s purity level. • Purity level is the extent to which the function is free of side effects, which refers to accessing database tables, package variables, and so on, for reading or writing. • It is important to control side effects because they can: • Prevent the proper parallelization of a query • Produce order-dependent and, therefore, indeterminate results • Require impermissible actions such as the maintenance of package state across user sessions

  32. Controlling Side Effects of PL/SQL Subprograms • To be callable from SQL statements, a stored function must obey the following purity rules to control side effects: • When called from a SELECT or a parallelized DML statement, the function cannot modify any database tables. • When called from a DML statement, the function cannot query or modify any database tables modified by that statement. • When called from a SELECT or DML statement, the function cannot execute SQL transaction control, session control, or system control statements.

  33. Package Function in SQL: Example CREATE OR REPLACE PACKAGE taxes_pkg IS FUNCTION tax (p_value IN NUMBER) RETURN NUMBER; END taxes_pkg; / CREATE OR REPLACE PACKAGE BODY taxes_pkg IS FUNCTION tax (p_value IN NUMBER) RETURN NUMBER IS v_rate NUMBER := 0.08; BEGIN RETURN (p_value * v_rate); END tax; END taxes_pkg; / SELECT taxes_pkg.tax(salary), salary, last_name FROM employees;

  34. Lesson Agenda • Overloading package subprograms, using forward declarations, and creating an initialization block in a package body • Managing persistent package data states for the life of a session and using PL/SQL tables and records in packages

  35. Persistent State of Packages • The collection of package variables and the values define the package state. The package state is: • Initialized when the package is first loaded • Persistent (by default) for the life of the session: • Stored in the User Global Area (UGA) • Unique to each session • Subject to change when package subprograms are called or public variables are modified • Not persistent for the session but persistent for the life of a subprogram call when using PRAGMA SERIALLY_REUSABLE in the package specification

  36. Persistent State of Package Variables: Example State for Jones State for Scott

  37. Persistent State of a Package Cursor: Example CREATE OR REPLACE PACKAGE curs_pkg IS –- Package spec PROCEDURE open; FUNCTION next(p_n NUMBER := 1) RETURN BOOLEAN; PROCEDURE close; END curs_pkg; CREATE OR REPLACE PACKAGE BODY curs_pkg IS –- Package body CURSOR cur_c IS SELECT employee_id FROM employees; PROCEDURE open IS BEGIN IF NOT cur_c%ISOPEN THEN OPEN cur_c; END IF; END open; . . . -- code continued on next slide

  38. Persistent State of a Package Cursor: Example . . . FUNCTION next(p_n NUMBER := 1) RETURN BOOLEAN IS v_emp_id employees.employee_id%TYPE; BEGIN FOR count IN 1 .. p_n LOOP FETCH cur_c INTO v_emp_id; EXIT WHEN cur_c%NOTFOUND; DBMS_OUTPUT.PUT_LINE('Id: ' ||(v_emp_id)); END LOOP; RETURN cur_c%FOUND; END next; PROCEDURE close IS BEGIN IF cur_c%ISOPEN THEN CLOSE cur_c; END IF; END close; END curs_pkg;

  39. Executing the CURS_PKG Package

More Related