It sure would be nice if..

[ScottMattes]

when using the Test Window to test some code that only exists in the Test Window if I could put my cursor over a Test Window variable and see the value during execution.

 

[Marco Kalter]

Unfortunately you can only see variable values that reside in stored program units.

 

[ScottMattes]

ctl-m is GREAT! It would be AWESOME if there was a way to hilight the stuff between the delimiters (inclusive). So, if I was on the '(' and I did something like ctl-shift-m then everything between the '(' and the matching ')' were hilighted (including the '(' and ')'.

Melody said so.

 

[ScottMattes]

That seems odd. PLSD is able to show watched vars at each line executed. I'll take your word for it; I can always make the code into a SP and use the Test Window to call it.

Thank you.

 

[ScottMattes]

the SQL window would
- have line numbers
- tell which line had the error (like SQL Plus does).

 

[Marco Kalter]

ctl-m is GREAT! It would be AWESOME if there was a way to hilight the stuff between the delimiters (inclusive). So, if I was on the '(' and I did something like ctl-shift-m then everything between the '(' and the matching ')' were hilighted (including the '(' and ')'.

Version 6.0 will automatically highlight parentheses and other structures (loop/if/case).

the SQL window would
- have line numbers
- tell which line had the error (like SQL Plus does).

The cursor will be located at the error position after an error.

 

[William Robertson]

ALTER xxx COMPILE DEBUG;
is only possible with stored code. Presumably this is why you can't watch variables in an anonymous block.