Home
Extending HCL OneDB™Beyond standard relational database objects, HCL OneDB™ can be extended to handle specialized data types, access methods, routines, and other objects. HCL OneDB™ includes many built-in extensions that are fully integrated in the database server. HCL OneDB™ also provides DataBlade® modules, which are packages of extended database objects for a particular purpose and that are installed separately from the database server. Alternatively, you can create your own user-defined objects for HCL OneDB™.
Creating extensionsYou can create user-defined data types, routines, access methods, and other database objects to suit your needs. You can use application programming interfaces to write user-defined routines and applications that access data in HCL OneDB™ databases.
DataBlade® API Function ReferenceThe HCL OneDB™ DataBlade® API Function Reference describes the DataBlade® API functions and the subset of functions that the DataBlade® API supports.
Function descriptionsThis section gives comprehensive reference information about the functions that are valid within DataBlade® API modules. It lists the function descriptions in alphabetical order, with syntax, usage information, and return values for the functions.
The mi_trigger_name() functionThe mi_trigger_name() function returns the name of the currently executing trigger.

The mi_trigger_name() function

The mi_trigger_name() function returns the name of the currently executing trigger.

Syntax

mi_string *mi_trigger_name(void)


Valid in client LIBMI application?	Valid in user-defined routine?
No	Yes

Usage

The mi_trigger_name() function queries the database server for the table on which the trigger is being is executed and returns the values of the owner name and the trigger name. This function can be called in SPL trigger functions and trigger procedures only within the triggered action list of the FOR EACH ROW clause in trigger definitions.

Return values

ownername.triggername: The name of the currently executing trigger.
NULL: The UDR is currently not executing as a part of trigger action.