• PL/SQL "continue" keyword – Now PL/SQL will allow a continue in a loop similar to one provided by C language, which can skip an iteration to bypass any “else” Boolean conditions. Below is an excellent PL/SQL example of the PL/SQL continue clause in-action:
BEGIN
FOR i IN 1..10
LOOP
DBMS_OUTPUT.PUT_LINE(’i=’||TO_CHAR(i));
IF ( i = 9 ) THEN
CONTINUE;
END IF;
DBMS_OUTPUT.PUT_LINE(’Only if i is not equal to 9′);
END LOOP;
END;
• Disabled state for PL/SQL - Another 11g new feature is a "disabled" state for PL/SQL (as opposed to "enabled" and "invalid" in dba_objects).
• Easy PL/SQL compiling - Native Compilation no longer requires a C compiler to compile your PL/SQL. Your code goes directly to a shared library.
• Improved PL/SQL stored procedure invalidation mechanism - A new 11g features will be fine grained dependency tracking, reducing the number of objects which become invalid as a result of DDL.
• Scalable PL/SQL - The next scalable execution feature is automatic creation of "native" PL/SQL (and Java code), with just one parameter for each type with an "on/off" value. This apparently provides a 100% performance boost for pure PL/SQL code, and a 10%-30% performance boost for code containing SQL.
• Enhanced PL/SQL warnings - The 11g PL/SQL compiler will issue a warning for a "when others" with no raise.
• Stored Procedure named notation - Named notation is now supported when calling a stored procedure from SQL.
Showing posts with label oracle 11g PLSQL new features. Show all posts
Showing posts with label oracle 11g PLSQL new features. Show all posts
Wednesday, July 16, 2008
Subscribe to:
Posts (Atom)