Jason,

Is your request more desirable to you than the insert statement
because the input params sent to the procedure are being manipulated
or inserted into multiple tables?

Markus

Jason Wharton wrote:

>
> I would like to suggest an enhancement to the SQL capabilities of InterBase
> and wonder what the architectural feasibilities of them are.
>
> In the same way you can do this:
>
> INSERT INTO ATABLE ( <list of columns> )
> SELECT <list of columns>
> FROM ANOTHERTABLE
> WHERE <record selection criteria>
>
> I would like to be able to do this:
>
> EXECUTE PROCEDURE APROCEDURE ( <list of columns> )
> SELECT <list of columns>
> FROM ANOTHERTABLE
> WHERE <record selection criteria>
>
> What has to be done right now is to write an additional stored procedure
> with a FOR SELECT and then in it's loop call the EXECUTE PROCEDURE
> statement. This is really a pain to have to do and not only that you cannot
> dynamically adjust the where clause of the SELECT that determines the
> records filtered into the stored procedure because that part is actually in
> a stored procedure too.
>
> This seems like it should be a simple allowance but I wonder if there is
> anything more to it than meets the eye. I suspect it might have something to
> do with the EXECUTE PROCEDURE construct being able to return results whereas
> the INSERT statement does not.
>
> All comments and suggestions appreciated.
>
> Jason Wharton
> CPS - Mesa AZ
> http://www.ibobjects.com
>
> ------------------------------------------------------------------------
> Best friends, most artistic, class clown Find 'em here:
> http://click.egroups.com/1/5533/4/_/830676/_/961115474/
> ------------------------------------------------------------------------
>
> To unsubscribe from this group, send an email to:
> IB-Architect-unsubscribe@onelist.com