Object-PL/SQL: Difference between revisions

Revision as of 02:40, 20 April 2012

Revision as of 02:42, 20 April 2012

Line 3:

Although PL/SQL's general [[Syntax (programming languages)|syntax]] formerly used to resemble that of [[Ada (programming language)|Ada]] or [[Pascal (programming language)|Pascal]], there were many improvements that include mainly the ''Java embedding code''<ref name="STKOVER">{{cite web|url=http://stackoverflow.com/questions/70072/when-should-you-use-java-stored-procedures-with-an-oracle-database-what-are|title=When Should you use Java Stored Procedures with an Oracle Database, what are the Drawbacks?|publisher=Stack Overflow|accessdate=15 April 2012}}</ref> and the ''object-oriented syntax''<ref name="ETUT">{{cite web|url=http://etutorials.org/SQL/Oracle+PL+SQL+Language+Pocket+Reference/Chapter+1.+Oracle+PLSQL+Language+Pocket+Reference/1.16+Oracles+Object-Oriented+Features/|title=Oracle's Object-Oriented Features|publisher=etutorial.org|accessdate=16 April 2012}}</ref> inside the SQL.

The mixing and embedding, in [[Database trigger|triggers]] and [[stored procedure]]s of the Java and the SQL languages was one of the breakthrough points up to support the ususe of [[PL/SQL]] in a ''OO'' paradigm<ref name="SAMS">Benett, 2002:144</ref>. The including in the SQL syntax of statements like <nokikinowiki>[class].[object]</nowiki>, the implementation of the object ''type''<ref name="TOP10"/> (like any OO language) completed the minimum requisites to a mapping approach in an extended SQL language without use of [[Persistence framework|specific mapping software]]<ref name="BALES">Bales, 2007:107-209</ref>.

== Autonomy, notoriety and importance of O-PL/SQL ==