I think the suspend is the bit where the procedure stalls long enough
for the calling routine to print a row or process the row.
If you only use procedure to massages data etc, you prolly have no need
of a suspend.

mattc

On Thu, 2003-10-23 at 07:56, peter@... wrote:
> Hi
>
> I notice in an awful lot of the store procedures examples there is a a SUSPEND statement towards the end.
> I am using several stored procedures in my application but I do not use the SUSPEND statement.
>
> Is this a problem / bad practice, I've not met any problems so far but I am a little concerned I may have a problem later.
>
> Rgds
>
> Peter
>
>
> eg. a simple example
>
> SET TERM ^^ ;
> CREATE PROCEDURE P_FIND_UNSOLD_VOUCHER returns (VOUCHER_ID Integer, ID Integer)
> AS
> /*
> Procedure: P_FIND_UNSOLD_VOUCHER
>
> Author : PJC
> Date : 15/sept/2003
> Purpose : to find an unsold voucher for voucher return function
> Params none, only uses Status = 0 , which is available
> ------
> <param> : <purpose>
> */
> begin
> /* code */
> SELECT First 1 VOUCHER_ID,ID from PINS where STATUS = 0
> INTO :VOUCHER_ID,:ID ;
> end
> ^^
> SET TERM ; ^^
>
> [Non-text portions of this message have been removed]
>
>
>
> To unsubscribe from this group, send an email to:
> firebird-support-unsubscribe@yahoogroups.com
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>


Maplin Electronics Ltd.
www.maplin.co.uk

This message is intended only for the use of the person(s) ("The intended
recipient(s)") to whom it is addressed. It may contain information which is
privileged and confidential within the meaning of applicable law. If you
are not the intended recipient please contact the sender as soon as possible.
The views expressed in this communication may not necessarily be the views
held by Maplin Electronics Ltd.