Sql statements executed in 10gR2 when pl/sql developer starts

[kino]

when pl/sql Developer Start, it execute some sql statements, Among them, below statement show bad performance and use high cpu resources.
.
select s.synonym_name object_name, o.object_type
from sys.all_synonyms s, sys.all_objects o
where s.owner in ('PUBLIC', user)
and o.owner = s.table_owner
and o.object_name = s.table_name and o.object_type in ('TABLE', 'VIEW', 'PACKAGE','TYPE'
, 'PROCEDURE', 'FUNCTION'
, 'SEQUENCE')
.
According to Oracle, in 10.1.0.5 or higher version, all_synonyms & all_objects have more complex plan than ealier version because of functional & security reason.
.
Oracle offer an workaround to create another view whose source is that of 10.1.0.4 or lower version DB, create private synonym for the user executing these statements, and use this private synonym instaed of public synonym.
.
but the workaround oracle offerd does'nt work in case of PL/SQL Developer Starting SQL Statement 'cause this use sys.all_objects, sys.all_synonyms.
.
I was wondering if the are any way of changing this sql statements PL/SQL Developer execute when it starts, bypassing or using dba views instead of all views??
.

 

[Marco Kalter]

This is currently not possible, but I have added this to the list of enhancement requests.

Note that this query runs in the background once afer you log on, so it doesn't happen often, and it does not cause a delay. To prevent this query, you can alternatively go to Tools > Preferences > User Interface / Code Assistant, and disable the "Describe Context" option. As a result, the Code Assistant will no longer suggest database object names when typing part of the name.

 

[kino]

Thanks for your reply..
.
And There is another question.
.
Would it be possible that this sql statement can use just all_objects, all_synonyms instead of sys.all_objects, sys.all_syonyms.
.
if possible, then we can use the workaround that oracle offered.

 

[Marco Kalter]

If we implement the enhancement request that you can override the default query, you can also omit the sys prefixes.

 

[kino]

OK, I'will wait for the ER to be implemented.
.
and then in which version do i see the ER implemented?
.
and how I am kept informed of the ER status?
When I get the workaround of bypass or omitting sys. schema?
.
I will notice that developers should disable "Discribe Context" in order to avoid performance problem. if then, they will ask until when they disable the useful funcion, and then I should provide answer.
.
Plz let me know approximate time the ER will be implemented.

 

[Marco Kalter]

I don't have a planned date yet, but maybe we can add this in 7.1. It's a relatively simple change.

 

[Michael Kirbach]

Hello Marco,

is the change for overriding the default query already part of the current version? We have high CPU load on a customer production system caused by the default query and we would like to keep at least the context functionality for tables.

Thanks in advance.
Michael

 

[Marco Kalter]

No, not yet. This is in the upcoming 9.0 release though. You can specify one or more queries to override the default query for name completion by the Code Assistant.

 

[Michael Kirbach]

Thanks for the information.