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_get_transaction_id() functionThe mi_get_transaction_id() function obtains the current internal transaction ID.

The mi_get_transaction_id() function

The mi_get_transaction_id() function obtains the current internal transaction ID.

Syntax

mi_integer mi_get_transaction_id(void);


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

Usage

The mi_get_transaction_id() function obtains the internal transaction ID of the current transaction. This transaction ID is not the same as the thread ID or the session ID. If mi_get_transaction_id() is called while not inside a transaction or with a non-logging database, it returns MI_ERROR. The value of the MI_ERROR -1.

Return values

>0: A transaction ID.
-1: indicates no transaction