> > > well, this gives some weight to a proposal to throw exception on
> > > SELECT from procedures without SUSPEND -- for I have made such mistake
> > > more than once.
> >
> > EXECUTE BLOCK with outputs semantically fully equal to
> > SELECT * FROM stored procedure
> And will silently return empty "resultset" if I forget to add SUSPEND?

Yes, exactly.

> > If you wish, you may read "doc\sql.extensions\README.execute_block"
> > which is available near the year :
> >
> > Since EXECUTE BLOCK is generated from client-side it's not needs
> > to have default parameters
> Thanks, now I understand.

Good ;)

> Actually, I was fooled by similiarity between
> CREATE PROCEDURE p (x INTEGER = 1)
> and
> EXECUTE BLOCK (x INTEGER = ?)
> They are, of course, totally different.

Yes

Regards,
Vlad