Plsql_optimize_level = 3 and native compilation in SQL Developer?

Question

SQL Developer: Version 3.1.06 (Build MAIN-06.82)
Oracle: 11gR2
OS: Ubuntu 10.10
Whenever I compile a PL/SQL unit in SQL Developer (using 'Compile' button) it is compiled with the following settings:
PLSQL_OPTIMIZE_LEVEL = 2
PLSQL_CODE_TYPE = 'INTERPRETED'
However, if I issue the following commands in an SQL Worksheet:
ALTER SESSION SET plsql_optimize_level = 3;
ALTER PACKAGE PACKAGE_NAME COMPILE PLSQL_CODE_TYPE = NATIVE;
the query SELECT PLSQL_OPTIMIZE_LEVEL, PLSQL_CODE_TYPE FROM ALL_PLSQL_OBJECT_SETTINGS WHERE NAME = 'PACKAGE_NAME'; resullts in
PLSQL_OPTIMIZE_LEVEL     PLSQL_CODE_TYPE
3     NATIVE
3     NATIVE
Is it possible to make SQL Developer to use these settings by default?
P.S. It seems that Tools > Preferences > Database > PL/SQL Compiler menu section is missing the options I need (Optimization level drop-down menu have numbers 0-2, but not 3). Are there any plans to support these features in the future releases?
Edited by: Ravshan Abbasov on Feb 6, 2012 6:28 AM

Answer 1

Hi Ravshan,
I thought a workaround would be to create a sql script like the following:
alter session set plsql_code_type=native;
alter session set plsql_optimize_level=3;  then point to it in the setting for Tools|Preferences|Database|Filename for connection startup script. That doesn't work however, as the other preference setting for plsql_optimize_level overrides the session value of 3 during compilation from the UI.
According to Oracle documentation, level 3 was added for Oracle 11g. Prior to that, the same effect could be achieved by level 2 in conjunction with the INLINE pragma in the PL/SQL code.
You might want to make a feature request for this on the SQL Developer Exchange so the community can vote and comment.
Regards,
Gary
SQL Developer Team
Edited by: Gary Graham on Feb 6, 2012 2:32 PM
And, of course, Compile for Debug does not work with the 'native' setting.