| Subject | Re: [firebird-support] Calling stored procedure in a trigger |
|---|---|
| Author | Helen Borrie |
| Post date | 2010-10-02T01:48:53Z |
At 12:45 PM 2/10/2010, Michael Ludwig wrote:
a) if that SSP is needed for direct output to a user application then create an executable procedure for use in PSQL modules
or
b) if that is the only place the SSP is used, then it shouldn't be a SSP at all, but an executable one with returning_values.
It seems to be just one more of those places where people try to do something against recommendations, for no better reason than "it seemed to work OK when I tested it". Then, when a situation comes up where it fails, they start asking how to fix it.
./heLen
>That section (Chapter 7, "Stored Proecedure Language (PSQL)", PDF pageMy mistake? I thought the OP was questioning why ROW_COUNT did not seem to "work" the way he had used it.
>51 (61) ff) does not readily yield the answer to the OP's question.
>
>I think you meant to be referring to something else.
>Anyhow, calling aBut why would you call a SSP from inside a trigger (or as a procedure call in *any* PSQL module)?
>selectable stored procedure from inside the trigger and using the return
>values works. Here's an example:
a) if that SSP is needed for direct output to a user application then create an executable procedure for use in PSQL modules
or
b) if that is the only place the SSP is used, then it shouldn't be a SSP at all, but an executable one with returning_values.
It seems to be just one more of those places where people try to do something against recommendations, for no better reason than "it seemed to work OK when I tested it". Then, when a situation comes up where it fails, they start asking how to fix it.
./heLen