Procedure Event

The event available for creating procedure event handlers is described below. Review the API documentation for procedure events for more information.

Execute Procedure

The Execute Procedure event fires whenever a procedure execution is requested. This request can be from processing SQL input, a direct invocation of a procedure by a client or script, or a portion of a compound procedure.

Possible uses:

Custom procedure—You can implement a procedure using other procedures, low-level navigation, recordset manipulation, or external data sources.
Validate inputs or filters—Host Integrator has limited support for validation, but an event handler can extend this capability.
Transform inputs or filters—The internal host codes may differ from the way data is passed in from a client or script.
Alter the results—Edit the result set by adding or removing records, transforming from internal to external representations of data, or storing the results in an external system (database) in lieu of returning them to the client.

Notes:

The default callback executes the entire model-defined procedure with provided filters or inputs, returning any results to the event handler for post-processing. For select, update and delete procedures there can be only one set of input parameters. For insert procedures, there may be one or more sets of input parameters.

Compound procedures cannot have events attached to them.