Object-PL/SQL

Object-PL/SQL (Object-Procedural Language/Structured Query Language or simply O-PL/SQL) is a methodology of using the Oracle Corporation's procedural extension language for SQL and the Oracle relational database.[1] [2] The additional features from version 7 and other improvements, lead to one of the large-scale environment implementations of the object-oriented database paradigm.[3]

Although PL/SQL's general syntax formerly used to resemble that of Ada or Pascal, there were many improvements that mainly include the Java embedding code[4] and the object-oriented syntax[5] inside the SQL.

The mixing and embedding of triggers and stored procedures was one of the breakthrough points up to support the use of PL/SQL in a OO paradigm.[6] The inclusion in the SQL syntax of statements such as [class].[object], and the implementation of the object type[7] (like any OO language), completed the minimum requisites to a mapping approach in an extended SQL language without use of specific mapping software.[8]

Autonomy, notoriety and importance of O-PL/SQL

The O-PSL/SQL isn't simply the use a version of a programming language but it's identified as how to use it, and it defines the autonomy of the theme.[9] Each version of PL/SQL, starting from 7, brings so many innovations that it's impossible to treat such usages as sub-themes of PL/SQL. So big is that revolution that it establishes a real borderline between the language, that can be used as formerly, and the OO approach inside itself. It's just this approach that makes the theme important and the large-scale using has brought its notoriety.[10]

A confusing of objects

There can be confusion of the notions of object of DBMS and of class object. This is very important as we live with both significances in one language. It's necessary to identify when the documentation refers to an object as one of the two definitions.

Database objects are concepts that refer to relational or sequential databases and persist being valid in new models. Tables, triggers, columns, indexes are examples of database objects,[7] which are present in O-PL/SQL, but with the same meaning of the notion of Java objects, specifically an element of a set that has its existence beginning from an instantiation of a class.

The PL/SQL
Main article: PL/SQL

PL/SQL is the extended SQL language used by Oracle Database.

PL/SQL is available in Oracle Database (since version 7), TimesTen in-memory database (since version 11.2.1), and IBM DB2 (since version 9.7).[11]

O-PL/SQL allows the definition of classes and instantiating these as objects, thus creating user-defined datatypes as writing constructors, beyond using Java in stored procedures and triggers.

Examples of uses of syntax of O-PL/SQL

Here is a small set of examples of O-PL/SQL syntax, extracted from the official documentation[12] and other sources:

A simple example of object-oriented PL/SQL[13]

create or replace type base_type as object (
  a number,
  constructor function base_type return self as result,
  member function  func return number,
  member procedure proc (n number)
) instantiable not final;
/

Now, the type's implementation is created. The implementation defines how the type's functions, procedures and how explicit constructors behave:

create or replace type body base_type as 
  constructor function base_type return self as result is
  begin
    a:=0;
    return;
  end base_type;

  member function func return number is
  begin
    return a;
  end func;

  member procedure proc (n number) as
  begin
    a:=n;
  end proc;
end;
/

We're ready to derive from base_type. The keyword for deriving is under. The derived type defines a new attribute (named: m) and overrides func.

create or replace type deriv_type under base_type (
  m number,
  overriding member function func return number
);
/

As is the case with base types, the overridden methods in the derived type must be implemented:

create or replace type body deriv_type as
  overriding member function func return number is
  begin
    return m*a;
  end;
end;
/

The created types can be instantiated and methods can be called:

declare
  b1 base_type :=base_type();
  b2 base_type :=base_type(4);
  d1 deriv_type:=deriv_type(5,6);
  d2 deriv_type:=deriv_type(5,6);
begin
  dbms_output.put_line(b1.func);
  dbms_output.put_line(b2.func);

  d1.proc(4);
  dbms_output.put_line(d1.func);
  dbms_output.put_line(d2.func);
end;
/

Results

0
4
24
30

The created types have become real types and can be used in tables:

create table table_base (
  b base_type
);
declare
  base  base_type := base_type();
  deriv deriv_type:= deriv_type(8,9);
begin
  insert into table_base values(base);
  insert into table_base values(deriv);
end;
/
select t.b.func() from table_base t;

Results:

0
72
select avg(t.b.func()) from table_base t;

Result:

36
gollark: I mean, functions/types are actually scoped.
gollark: I don't know exactly how OCaml modules work, but they seem generally saner?
gollark: It's WORSE, not better. Importing a module should actually isolate the functions in it to a scope or something unless you explicitly don't want that, and apparently the .h thing makes compilation more bees.
gollark: There's no namespacing.
gollark: I don't count header files as modules.

See also

Bibliography
  • Bennett, Mathew (2002). Programming Oracle Developer (1 ed.). Indianapolis: Sams. p. 348. ISBN 0672321106.
  • Bales, Donals (2007). PL/SQL from Novice to Professional (1 ed.). New York: Apress. p. 469. ISBN 978-1590598825.
  • Feuerstein, Steven; Pribyl, Bill (2009). "26". Oracle PL/SQL Programming. Sebastopol: O'Reilly Media, Inc. ISBN 9780596514464.
  • Rahayu, Wenny; taniar, David; Pardede, Eric (2006). Object-Oriented Oracle (PDF). Hershey: IRM Press. p. 345. ISBN 1591406080. Archived from the original (PDF) on 2016-03-03. Retrieved 2012-04-20.

References
  1. Lassan, Alan R.; Due, Jacob Steen (13 June 2000). "Experiences with Object Oriented Development in PL/SQL" (PDF). The danish National Center for IT Research. Archived from the original (PDF) on 24 December 2010. Retrieved 15 April 2012.
  2. Centre For; Allan R. Lassen; Jacob Steen Due (2000). "Experiences with Object Oriented Development in PL/SQL". CiteSeerX 10.1.1.38.5122. Cite journal requires |journal= (help)
  3. Cunningham, Lewis. "PL/SQL Features by Release". Burleson Consulting. Retrieved 15 April 2012.
  4. "When Should you use Java Stored Procedures with an Oracle Database, what are the Drawbacks?". Stack Overflow. Retrieved 15 April 2012.
  5. "Oracle's Object-Oriented Features". etutorial.org. Retrieved 16 April 2012.
  6. Benett, 2002:144
  7. Shubho, Al-Farooque (8 November 2009). "Optimize Database Files and Apply Partitioning". The Code Project. Retrieved 19 April 2012.
  8. Bales, 2007:107-209
  9. "Use Object PL/SQL". java2s.com. Retrieved 19 April 2012.
  10. Feuerstein, 2009
  11. "DB2 10: Run Oracle applications on DB2 10 for Linux, UNIX, and Windows". IBM. Retrieved 20 April 2012.
  12. "Oracle Documentatio". Oracle. Retrieved 19 April 2012.
  13. "Object Oriented Oracle, example 1". René Nyffenegger's collection of things on the web. Retrieved 19 April 2012.

External sources


This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.