> What is the problem here? Is it that Jaybird cannot accept a SELECT
> statement for CallableStatement?

No, it can't and that's not specification conformant. Only {call ...}
syntax is officially allowed.

> Or that it can, but it can't be taught
> that if you get both SELECT and a FROM clause consisting of an
> identifier and a bracketed tuple of arguments, then it is a call to
> a selectable stored procedure?

That's I do not want to do. And I do not need to - API is quite
uniform here. In both cases I have to prepare the in and out XSQLDA
and in both cases I get results almost the same way.

> If the programmer submits a SELECT statement for an executable SP,
> then that is a programmer error.

Probably, but why? Because Firebird is implemented so, that was good
for our fathers, and for farthers of our fathers, and so on?

And why EXECUTE PROCEDURE should deliver me wrong (empty) result when
used with selectable procedure?

> Why would they have to change their applications? The driver should
> make the proper decision according to the SQL statement supplied by
> the application.

Application supplies my "{call ...}", it is my responsibility to
convert it into either SELECT * FROM or EXECUTE PROCEDURE. And I can't
without additional hint from the application.

Roman