Default Parameters in a Stored Procedure Hook
In OneData, you can specify the parameters to the external program or stored procedure when you define the hook or assign it to an object. Parameters defined when the hook is assigned to an object, the parameters override the parameters in the hook definition.
You can use static parameters as needed. You can also pass any other constant numeric parameters to the procedure other than the following placeholders.
Note:
The following rules apply to parameters:
Parameters are not case sensitive and must be separated by commas.
The format for dates in the XML data stream is YYYY-MM-DD HH24:MI:SS.
The XML stream publishes BLOB and CLOB as null values.
Default Parameters for Validation in Pre-Process Mode for Database Hooks
%TABLE_NAME% | Physical table name of the object associated with the hook. |
%TRANSACTION_ TYPE% | Data manager action that triggers the stored procedure. Valid values: I (Insert) U (Update) D (Logical delete) R (Restore) P (Purge or physical delete) |
%DATA_XML% | XML format of the record being manipulated. Column names as XML tags. |
%USER_ID% | User ID of the user performing the data change or executing the hook command. |
%DATA_XML_TEXT% | Passes XML to a hook using string data type. |
Pre-Defined Parameters for iHooks
%IN_XML% | XML format of the record being manipulated. OneData internally stores the XML data as a BLOB. |
%OUT_XML% | Output XML from iHook that OneData returns as BLOB. |
%MTCHG_ENGN_ XML% | XML string that the matching engine returns if matching rules are defined. |
Note:
If the values that you pass contain only numbers, define the parameter as long or string.