Claus Pedersen
Member³
I have a test script with the following content:
When I write 'to_char' and the opening paranthesis '(' , the developer 'stalls' for about one minute before I can write the finishing code. It seems that it is the describing of to_char that takes quite a while.
I have run the test script with the debugsql parameter turned on and investigated the debug.txt file.
PLD runs a script (PLSQLDevForm.ResolveSymbolQuery2) to find out what to_char refers to. The first time it is run with the parameters
ART1 = TO_CHAR
:CUR_SCHEMA =
on 0.3 sec.
Then the select
is run on approx. 9 seconds.
Then script PLSQLDevForm.ResolveSymbolQuery2 is run again, this time with parameters
ART1 = SYS
ART2 = STANDARD
ART3 = TO_CHAR
:CUR_SCHEMA =
on 0.3 sec.
Then there is a time span of 54 (!) seconds where apparently nothing happens. The next entry in debug.txt says
LoadFileList: C:\DOCUME~1\NNN\LOCALS~1\Temp\PLS-Recovery\722336.*
What happens in these 54 seconds?
Developing on a connection having these kind of waiting periods where PLD freezes for about a minute each time you type an opening paranthesis, quickly takes the fun out of work.
Can somebody shed a light on this?
P.S. I know that I can disable describing of standard functions in the code assistant setup, but I switch back and forth between local connections and connections made via VPN, so for me this solution is not optimal.
Code:
declare
i integer;
begin
i := to_char ('1');
end;
When I write 'to_char' and the opening paranthesis '(' , the developer 'stalls' for about one minute before I can write the finishing code. It seems that it is the describing of to_char that takes quite a while.
I have run the test script with the debugsql parameter turned on and investigated the debug.txt file.
PLD runs a script (PLSQLDevForm.ResolveSymbolQuery2) to find out what to_char refers to. The first time it is run with the parameters

:CUR_SCHEMA =
on 0.3 sec.
Then the select
SQL:
select text
from sys.all_source
where owner = 'SYS'
and name = 'STANDARD'
and type = 'PACKAGE'
order by line
is run on approx. 9 seconds.
Then script PLSQLDevForm.ResolveSymbolQuery2 is run again, this time with parameters



:CUR_SCHEMA =
on 0.3 sec.
Then there is a time span of 54 (!) seconds where apparently nothing happens. The next entry in debug.txt says
LoadFileList: C:\DOCUME~1\NNN\LOCALS~1\Temp\PLS-Recovery\722336.*
What happens in these 54 seconds?
Developing on a connection having these kind of waiting periods where PLD freezes for about a minute each time you type an opening paranthesis, quickly takes the fun out of work.
Can somebody shed a light on this?
P.S. I know that I can disable describing of standard functions in the code assistant setup, but I switch back and forth between local connections and connections made via VPN, so for me this solution is not optimal.