export objects filter

[Milan Martak]

Hello,
i try to force PLSQLDev to populate only objects that i want to see in the Export User Objects window instead of all user objects. No luck so far. A simple filter capability would definitelly please (for example select and apply an existing filter).
I have found this old topic though. Is there something i am missing or there was simply no urgency to get this feature implemented (if that is the case are there any plans for near future)?
Thanks
milan

 

[Marco Kalter]

If you double-click on a header in an object list, you can define a filter for the corresponding column, using wildcard characters (% and _). You can define multiple comma separated filters (e.g. emp%, dept% for everything that starts with emp or dept).

If you right-click on the object list you can subsequently save the current filter, or load a previously saved filter.

 

[Milan Martak]

Thank you.
This is very nice feature. However i hit the wall when i work with a large schema (imagine Oracle Applications with 10000 objects ...). When i try what you suggested then i have to wait untill all objects are populated and then i actually can load the filter - and then i have to wait again... imagine working remotely over VPN...
Any idea is welcome and if there is no other way that's fine too.
thanks
milan

 

[Milan Martak]

btw i am still waiting for the filter to complete

 

[Marco Kalter]

1:24 is a long time. We'll investigate why it might be so slow.

 

[DLab]

I am having the same issue. We have multiple environments on a single instance of a database containing lots of objects. Opening Export User Objects freeze the application for too long.

Using Version 7.0.2.1076

 

[DLab]

Further Information

Here is the query made by Pl/sql developer when I bring the export user objects view.

select *
from sys.all_objects o
where owner = 'THIS_OBJECT_OWNER'
and object_name not like 'BIN$%'
and object_type in ('PACKAGE', 'PACKAGE BODY', 'TYPE', 'TYPE BODY', 'FUNCTION', 'PROCEDURE', 'TRIGGER', 'JAVA SOURCE', 'LIBRARY', 'DIRECTORY','TABLE', 'SEQUENCE', 'VIEW', MATERIALIZED VIEW', 'SYNONYM')
and (object_type 'TYPE' or exists (select null from all_types t where t.owner = o.owner and t.type_name = o.object_name))

I have bolded the condition that cause this problem. all_types is a very slow view in environments with large number of objects like ours. it can take more than 1 full minute to retrieve all types by owner and around 2-3 seconds by owner and object_name. If we multiple this 2-3 seconds by 600 objects, we get around 20-30 minutes to retrieve this list. Now, if we remove this check, the list gets populated in 8 seconds. Any reason why this check on all_types view is occuring?