260 crashes if no plan

259/260 both crash out if execute a s/proc that has no plan (ie no data 
access sql)

It would be good if such cases did not even report the "no plan" msg 
dialogue as prev versions have done.

-- 
Brent Rose
Whats On Report
brent@whatson.co.nz

Brent Rose wrote:

> 259/260 both crash out if execute a s/proc that has no plan (ie no
> data access sql)
> 
> It would be good if such cases did not even report the "no plan"
msg
> dialogue as prev versions have done.

Brent,

Do you mean you get crashes when the sql statement is something like
execute procedure myproc?
I don't get crashes in that case, so I'm wondering what you are trying

Brent,
Thanks for the example.
First of all you don't need to include a "suspend" statement if you
don't return any rows.
Second: all previous versions of IBConsole crash when there is no plan.
IBConsole tries to fetch a plan for a select statement. The IBX however
raises a fatal exception when there is no plan. This causes the crash.

Gelein van de Voorde wrote:

> First of all you don't need to include a "suspend" statement if
you
> don't return any rows.

That is not correct. If the stored procedure has an output parameter
and you want the stored procedure to be selectable you must include
suspend. It makes no difference if the output parameter is filled with
a value from a column returned by SELECT or if it is filled with the
result of a calculation.

-- 

Thanks for the correction Bill.
I was mistake. I never use a select statement in such cases but a