> Another BDE hell...
>
> I'm wondering how driver architecture developers like to step
> on the same rake. Anyway, this is rithoric question.

Well, it works. :) Probably the main difference between BDE and JDBC
is that there is nothing like TTables, filters, local SQL processing
etc. there. And there are no visual tools. However there's auto-commit
there, and no commit retain :)

> As I understood there is no way to say to CallableStatement that
> procedure must be executed or selected. Right?

In standard JDBC - no. JayBird provides a FirebirdCallableStatement, a
subclass of CallableStatement with method setSelectableProcedure(boolean).

> If so, does other server's drivers behaive same, i.e. while they
> support output and resultset procedures, they always call procedures
> as resultsets?

This is not specified. I suspect that API for Oracle or MS SQL is
different. As a hint, if I know correctly, there is no SELECT * FROM
in Oracle - all procedures are called with CALL.

> Excuse me, I completely do not know JDBC specification
> and want to see if there any kind of calling CallableStatement other
> than you already gave.

At least I do not know anything else. Nobody prevents people to use
PreparedStatement for EXECUTE PROCEDURE or SELECT * FROM and then
accessing the values as result set, but that is not specification-conform.

Roman