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,
is there a chance, that the performance of the 'Find Database Object' functionality will be improved in the next release?
Thanks for your support.
Mike,
I agree on the benefits of PL/SQL Developer over SQL Navigator, especially the possibility to see and edit found search results already during run of the search. The feature to double click on the results of the search and jump to the occurrence in the database object, however is also...
Further analysis has shown:
...
The following statements are executed many times against the database, even if you are not specifying an object name:
select text from sys.all_source
where owner = :owner and name = :name and type = :type
order by line
select text from sys.all_source where...
Thanks for your reply:
If you compare the search masks of PL/SQL Devloper and SQL Navigator, you have more DB object types for selection/restriction. The rest looks similiar.
Anyway, if I restrict the search criterias on package specification/body and on one user, the search takes about 15...
Hi,
we are currently evaluating other PL/SQL development tools than the one we are currently using. So far we are quite impressed by the functionality of the PL/SQL Developer, but there is one important issue:
Using the 'Find database objects - Full text search' is showinq a very bad...