|Subject||Re: Re: [Firebird-Architect] RFC: Please unify stored procedure execution|
> If this so-called "unified execution" has to be introduced as aBecause there's no way to KNOW if a procedure is select-able. Is it?
> second-string *option* to stuff Firebird into this warpy mould, just don't
> make it a one-size-fits-all engine re-implementation that drags everyone
> else down to the lowest common denominator. Notwithstanding, I'd rather
> see the Jaybird developers find a way to make it work properly, and show
> the rest what they're missing. How hard is it to teach the driver that
> SELECT BLAH FROM APROC(?, ...) means it has to prepare a multi-row buffer,
> call EXECUTE PROCEDURE and start a fetch loop?
As far as I can tell, a procedure without "suspend" never returns values.
So using "select" when there are output parameters is not sufficient.
Using EXEC that would return a resultset (if available) would be very
easy to use... IMO of course.
Database Workbench - developer tool for InterBase, Firebird, MySQL & MS SQL