Ensuring backward compatibility, PL-SQL Programming

Assignment Help:

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;

Related Discussions:- Ensuring backward compatibility

Example of shorthand for a row constraint - sql, Example of Shorthand for a...

Example of Shorthand for a row constraint Example: Shorthand for a row constraint ALTER TABLE EXAM_MARK ADD CONSTRAINT Mark_in_range CHECK (Mark BETWEEN 0 AND 100);

Anatomy of a command, Anatomy of a Command Figure, showing a simple S...

Anatomy of a Command Figure, showing a simple SQL command, is almost identical to its counterpart in the theory book. The only difference arises from the fact that SQL uses a

If statement - syntax, IF Statement The IF statement executes a series ...

IF Statement The IF statement executes a series of statement conditionally. Whether the series is executed or not depends on the value of the Boolean expression. Syntax:

Recursive subprograms, Recursive Subprograms The recursive subprogram ...

Recursive Subprograms The recursive subprogram is the one that calls itself. Think of a recursive call as a call to a few other subprograms that does the similar task as your

Keyword & parameter description - expressions, Keyword & Parameter Descript...

Keyword & Parameter Description: boolean_expression: This is an expression which yields the Boolean value that is TRUE, FALSE, & NULL. character_expression: This

Join and and in sql, JOIN and AND in SQL In this Section is all about ...

JOIN and AND in SQL In this Section is all about one operator, JOIN. SQL's closest counterpart, NATURAL JOIN, has already been covered. Here we look at several other "join" op

Parameter and keyword description - update statement, Parameter and Keyword...

Parameter and Keyword Description: table_reference: This keyword identifies the table or view that should be accessible when you execute the UPDATE statement, and for wh

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;

Fetching across commits, Fetching Across Commits The FOR UPDATE clause...

Fetching Across Commits The FOR UPDATE clauses acquire exclusive all row locks. All rows are locked when you open the cursor, and when you commit your transaction they are unl

Overloading, Overloading The PL/SQL overloads the subprogram names. T...

Overloading The PL/SQL overloads the subprogram names. That is, you can use similar name for few different subprograms as long as their formal parameters differ in the number

Write Your Message!

Name

Email id

Message

Verfication Code

User Account

All Pages