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

Join query, Using a join on 3 tables, select 5 columns and 10 rows from the... Using a join on 3 tables, select 5 columns and 10 rows from the 3 tables without the use of a Cartesian product Query: SELECT E.LAST_NAME, E.FIRST_NAME, S.BUILDING, S.BRAN

Literals in pl/sql, Literals A literal is an explicit numeric, string... Literals A literal is an explicit numeric, string, character, or Boolean value not represented by an identifier. Numeric literal 147 and the Boolean literal FALSE are some of

Keyword, what is the use of declare keyword what is the use of declare keyword

Forward declarations - subprograms, Forward Declarations The PL/SQL ne... Forward Declarations The PL/SQL needs that you declare an identifier before using it. And hence, you should declare a subprogram before calling it. For illustration, the decla

Magento change address format depending on store, Magento change address fo... Magento change address format depending on store Project Description: What I need is that depending on the store in which the customer bought the address should change the fo

Introduction to SQl and DQL, which operation is used if we are interested i... which operation is used if we are interested in only certain columns of a table?

Sql, If two relations R and S are joined, then the non matching tuples of b... If two relations R and S are joined, then the non matching tuples of both R and S are ignored in __________________.

Group and having query, Using a join on 2 tables, select all columns and 10... Using a join on 2 tables, select all columns and 10 rows from the 2 tables without the use of a Cartesian product. Query: SELECT * FROM EMPLOYEE1 E JOIN STAFF S ON E.EMP_

Declaring exceptions - user-defined exceptions, Declaring Exceptions T... Declaring Exceptions The Exceptions can be declared only in the declarative part of the PL/SQL subprogram, block, or package. By introducing its name, you can declare an excep

Using not null-declarations in sql, Using NOT NULL Besides assigning an ... Using NOT NULL Besides assigning an initial value, the declarations can impose the NOT NULL constraint, as the example below shows: acct_id INTEGER(4) NOT NULL := 9999; You ca