At 11:25 PM 27-03-01 +1000, you wrote:

> > My comment is probably due to you simplifying your case to
> > make it understandable for the rest of us :o) But why do
> > you use SUSPEND when there's no SELECT in this procedure?
>
>Because I want to use the procedure as
>
>SELECT OUTVAL FROM CHANGEVAL( 'ABCD', 1 )

Then I can't see how you can avoid the memory-eating behaviour. SUSPEND is causing IB to append each row to an output dataset in memory as it is processed. It's all inside one transaction, isn't it, so the dataset is going to keep growing until the transaction completes.

Cheers,
Helen

> > My ancient language reference (IB 4.0) from long before I
> > started using IB says "Not recommended for executable
> > procedures".
>
>I've always interpretted this to mean procedures you intend to use in
>form:
>EXECUTE PROCEDURE CHANGEVAL...
>RETURNING_VALUES ....
>
>That is; it has nothing to do with the content of the stored
>procedure, only the way in which it will be called. If you take a
>look at the example (even in your ancient copy I suspect) you will see
>that there was no internal select statement in that code either.
>
>
>Geoff Worboys
>Telesis Computing
>
>
>
>To unsubscribe from this group, send an email to:
>ib-support-unsubscribe@egroups.com
>
>
>
>Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/

All for Open and Open for All
InterBase Developer Initiative · http://www.interbase2000.org
_______________________________________________________