Subject | Exexcutable Stored Procedures |
---|---|
Author | yahdominiek |
Post date | 2005-08-05T10:34:19Z |
Hi all,
FirebirdSS 1.5.2.4731
PHP 5.0.4-6
I've seen some examples of returning values from an *executable*
stored procedure by forcing it into a *selectable* stored procedure
with 'suspend'. This is however not how these two variants of stored
procedures are intended. An executable SP does not necessarily return
an output set, and if it does it's allways a single row. A 'suspend'
in an executable stored procedure renders the procedure unusable in
eg. DBExpress.
So far I've been using two variants of each of my SP's (one
selectable for PHP, one executable for FB-native clients) which is
tedious.
My question : is there no way to use an *executable* stored procedure
as it is intended ?
I found nothing on PHP.net or google except the aforementioned 'work-
arounds'.
Thanks,
Dominiek D'hondt
FirebirdSS 1.5.2.4731
PHP 5.0.4-6
I've seen some examples of returning values from an *executable*
stored procedure by forcing it into a *selectable* stored procedure
with 'suspend'. This is however not how these two variants of stored
procedures are intended. An executable SP does not necessarily return
an output set, and if it does it's allways a single row. A 'suspend'
in an executable stored procedure renders the procedure unusable in
eg. DBExpress.
So far I've been using two variants of each of my SP's (one
selectable for PHP, one executable for FB-native clients) which is
tedious.
My question : is there no way to use an *executable* stored procedure
as it is intended ?
I found nothing on PHP.net or google except the aforementioned 'work-
arounds'.
Thanks,
Dominiek D'hondt