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

Table comparison - sql, Table Comparison - SQL The following definitio... Table Comparison - SQL The following definitions for relation comparisons: Let r1 and r2 be relations having the same heading. Then: r1 ⊆ r2 is true if every tuple of r1

Disjunction - sql, Disjunction (OR, ∨) Again we have nine rows instead... Disjunction (OR, ∨) Again we have nine rows instead of just four and again, when unknown is not involved, the rows are as for 2VL. Also, when anything is paired with true, t

Interesting properties of cross join - sql, Interesting properties of CROSS... Interesting properties of CROSS JOIN - SQL Compare these with the "interesting properties of JOIN", CROSS JOIN is associative but not commutative. Unlike JOIN and NATURAL JOI

Need fullcalendar modifications, Project Description: I am looking to ch... Project Description: I am looking to change FullCalendar to add/delete sql server data when events are removed or dropped from Calendar. Events should only be included by dra

Selecting objects in pl sql, Selecting Objects: Suppose that you have ... Selecting Objects: Suppose that you have run the SQL*Plus script below that creates object type Person and object table persons, and that you have settled the table: CREATE

Manipulating collections-nested table examples, Manipulating Collections ... Manipulating Collections Within PL/SQL, the collections add procedural power and flexibility. The biggest benefit is that your program can compute subscripts to process the spec

Homework, What are the rates for help in writing PL/SQL procedures and func... What are the rates for help in writing PL/SQL procedures and functions?

Stored subprograms, Stored Subprograms Normally, tools (like Oracle Fo... Stored Subprograms Normally, tools (like Oracle Forms) which incorporate the PL/SQL engine can store subprograms locally for later, strictly local execution. Though, to become

Exception_init pragma - pl/sql, EXCEPTION_INIT Pragma The pragma EXCEPT... EXCEPTION_INIT Pragma The pragma EXCEPTION_INIT relates an exception name with an Oracle error number. Which allow you to refer to any internal exception by the name and to wri

Procedures - syntax, Procedures The procedure is a subprogram which can... Procedures The procedure is a subprogram which can take parameters and be invoked. Normally, you can use a procedure to perform an action. The procedure has 2 sections: the spe