Hi Marco
I ran some experiments here and am easily able to recreate the problem.
Open a new SQL Window, and enter this 10 line SELECT:
SELECT owner
,NAME
,TYPE
,line
,text
FROM user_source
ORDER BY owner
,NAME
,TYPE
,line;
Copy this and paste 100 times to make 1000 lines of code. Then make a new line and type another command, say
SELECT SYSDATE FROM DUAL;
Select the first 1000 lines, copy and paste 9 times to make 10000 lines before the SYSDATE command above. Then position the cursor in the SYSDATE command above (ensure you have auto select turned on) and hit the execute - you should notice a delay with "Initialising..." displayed on the status line, during which the application is locked.
Note that I tried with just 10000 blank lines, and with 10000 non-SQL lines, and the delay does not happen. So it is related to the application trying to parse the SQL command to be run from other SQL in the Window. Also, the more SQL command lines I add before the SYSDATE command, the longer the delay.
It must be said here that I am running the software on an old Dell Optiplex GS620 under Windows 2000 Professional, and perhaps with a more modern PC with faster processor/OS/more memory etc. there may not be much of a delay, or you may have to add a lot more SQL commands before the SYSDATE command until you see the delay.
If you need any more details, let me know.
Best regards
Billy
