> > Because there's no way to KNOW if a procedure is select-able. Is
> > it?
>
> There is way - existence of outputs.

Please use then example posted by Martijn - SELECT with procedure with
outputs without SUSPEND in its body. You get empty result set.

> Roman propose always return resultset, even if SP has no
> SUSPEND. But this can break existing applications. Therefore there
> are another proposition - use new special syntax for such call's.
> Ok... what else from JDBC\ADO\OLEDB\etc don't fit in FB's SQL
> dialect ? Will we make new syntax for every new client access
> layer ?
>
> If JDBC will follow simple rule about how to call our SP's and
> documented it i see no problem, sorry.

The problem is that people have to change their applications to
provide a hint to a driver to use SELECT.

Roman