test window and sessions

[dnador]

I have two questions hopefully someone can answer.
1. Is there a way to test a test script for validity before running it? Usually the script has to be killed to stop it and I like to confirm it is ok before I'm actually ready to run it.

2. Is there a way to customize the main sessions script. I like it to be ordered by status or only show active sessions.

Thanks for your time and for such a great product!
Dave

 

[Marco Kalter]

1. Is there a way to test a test script for validity before running it?

What exactly do you mean with 'validity'? Compilation errors will immediately be reported. Run-time errors can of course on be found at run-time

.

2. Is there a way to customize the main sessions script. I like it to be ordered by status or only show active sessions.

You cannot define the default sort order, but you can click on the sort buttons in the column header to set the primary and secondary sort column.

------------------
Marco Kalter
Allround Automations

 

[dnador]

Hi Marko...thanks for the reply...

I'll just keep using the column sort buttons...

What I mean by validate is just what you said about compilation errors. Since it's just a test script it doesn't compile. In fact i dont have permissions to compile a procedure in this case. I don't see any compile errors or runtime errors until I actually run it. I would like to be able to see the compile errors as if I were compiling a procedure without actually having to execute the script. Does that make sense?
I appreciate your time,
Dave

 

[Marco Kalter]

You mean that one or more of the program units that the Test Script calls is invalid? We could of course check that before execution.

------------------
Marco Kalter
Allround Automations

 

[dnador]

for instance....

declare
i integer;
begin
for i in 1..3 loop
select 5 from duaf;
end loop;
end;

in the test script above(run from a test window) the table duaf does not exist. I don't actually want to run this query right now because the server is too bust. I'm going to schedule a cron to run it at midnight. I don't want to wait til midnight to find out I typed the table in wrong. The way the test script works right now I can't test this. I have to actually execute the script to find out if something is wrong. If nothing is wrong it will run, which is what I don't want to do
Does this make sense?
Thanks,
Dave