strange command window behaviour due to line/block comment nesting

[Bernhard S]

I have created a command window with following test case content to better demonstrate the effect

-- this is a test how a block comment start sign
-- in a line comment affects execution of PSD command window /*
select sysdate from dual;

When executing this I get in the dialog sheet following output:

Connected to Oracle Database 10g Enterprise Edition Release 10.2.0.4.0
Connected as scott

SQL>
  3

Hitting enter just adds 4, 5, ...
A semicolon doesn't end the curse either. Only way to end it without quitting PSD is doing something like this:

SQL>
  3  */;

-- in a line comment affects execution of PSD command window /*
select sysdate from dual;
*/

ORA-00911: Ung

 

[Marco Kalter]

This is indeed a Command Window parsing bug. We'll fix it.