Object-PL/SQL: Difference between revisions

Revision as of 02:42, 20 April 2012

Revision as of 02:43, 20 April 2012

Line 1:

'''Object-PL/SQL''' ('''[[Object-oriented programming|Object]]-Procedural Language/[[Structured Query Language]]''' or simpllysimply '''O-PL/SQL''') is a methodology of usage of the [[Oracle Corporation]]'s [[Procedural programming|procedural]] extension [[programming language|language]] for [[SQL]] and the [[Oracle Database|Oracle relational database]]<ref name="CITDK">{{cite web|url=http://www.cit.dk/cot/reports/reports/Case4/18/cot-4-18.pdf|title=Experiences with Object Oriented Development in PL/SQL|author=Lassan, Alan R., Due, Jacob Steen|date=13 June 2000|publisher=The danish Nationl Center for IT Research|accessdate=15 April 2012}}</ref> after the features of the version 7 and further improvement<ref name="DBAORA">{{cite web|url=http://www.dba-oracle.com/t_edb_pl_sql_features_release.htm|title=PL/SQL Features by Release|author=Cunningham, Lewis|publisher=Burleson Consulting|accessdate=15 April 2012}}</ref>, leading to one of the means of large-scale environment implementations of the [[object-oriented database]] paradigm.

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.