Ensuring Backward Compatibility 

The PL/SQL Version 2 permits some abnormal behavior which Version 8 disallows.

Particularly, Version 2 permits you to

(i) Make the forward references to RECORD and TABLE types when declaring the variables.

(ii) Specify the name of the variable (not a datatype) in the RETURN clause of the function specification.

(iii) Assign values to the elements of an index-by table IN parameter.

(iv) Pass the fields of a record IN parameter to the other subprogram as OUT parameters

(v) Use the fields of a record OUT parameter on the right-hand side of the assignment statement.

(vi) Use the OUT parameters in the FROM list of a SELECT statement.

For backward compatibility, you might want to remain this particular Version 2 behavior. You can do it by setting the PLSQL_V2_COMPATIBILITY flag. At server side, you can set the flag in 2 ways:

(i) Add the line below to the Oracle initialization file:

PLSQL_V2_COMPATIBILITY=TRUE

(ii)Execute one of the SQL statements below:

ALTER SESSION SET PLSQL_V2_COMPATIBILITY = TRUE;

ALTER SYSTEM SET PLSQL_V2_COMPATIBILITY = TRUE;

Posted Date: 10/5/2012 5:02:58 AM | Location : United States

Ask an Expert

Related Discussions:- Ensuring backward compatibility, Assignment Help, Ask Question on Ensuring backward compatibility, Get Answer, Expert's Help, Ensuring backward compatibility Discussions

Write discussion on Ensuring backward compatibility
Your posts are moderated

Write your message here..

Related Questions

Compare sql and pl/sql, Question 1 . Compare SQL and PL/SQL Question 2 ... Question 1 . Compare SQL and PL/SQL Question 2 . Write a database trigger to implement the following check condition                          Given the following table

Select query, Query: SELECT * FROM EMPLOYEE1; Select 5 columns and ... Query: SELECT * FROM EMPLOYEE1; Select 5 columns and all rows from one table Query: SELECT C_ID, COMPANY, BUILDING, DEPARTMENT, BRANCH FROM CONTRACT;

Using prior and next - collection method, Using PRIOR and NEXT The PRI... Using PRIOR and NEXT The PRIOR(n) returns the index number that precede index n in a collection. The NEXT(n) returns the index number which succeed the index n. If n has no pr

Authorisations - privileges, Authorisations - Privileges As relational... Authorisations - Privileges As relational theory is silent on the issue of authorisation, it offers nothing with which SQL's vast edifice in support of what it calls privilege

Using aggregation on nested tables - sql, Using Aggregation on Nested Table... Using Aggregation on Nested Tables Example is the most direct translation of its counterpart in the theory book that can be obtained in SQL but it is so over-elaborate that no

Pragma restrict_references in pl sql, Using Pragma RESTRICT_REFERENCES: ... Using Pragma RESTRICT_REFERENCES: The function called from the SQL statements should obey certain rules meant to control the side effects. To check for violation of the rules,

Theory of special creation - origin of life, THEO R Y OF SPECIAL CREATION... THEO R Y OF SPECIAL CREATION - Life originated on the earth due to natural events by the super natural power. The biblical story of creation of world within six days was p

Positional notation, Positional Notation The first procedure call uses... Positional Notation The first procedure call uses the positional notation. The PL/SQL compiler relates the first actual parameter, account, with the first proper parameter, ac

Assignments in pl/sql, Assignments in pl/sql The Variables and constants... Assignments in pl/sql The Variables and constants are initialized every time a block or subprogram is entered. By default, the variables are initialized to NULL. Therefore, unle

Declaring a cursor, Declaring a Cursor The Forward references are not ... Declaring a Cursor The Forward references are not allowed in the PL/SQL. Therefore, you must declare a cursor before referencing it in other statements. Whenever you declare a