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_transaction_state() function (Server)The mi_transaction_state() function returns the current transaction state (none, implicit, or explicit).

The mi_transaction_state() function (Server)

The mi_transaction_state() function returns the current transaction state (none, implicit, or explicit).

Syntax

mi_integer mi_transaction_state()


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

Usage

The mi_transaction_state() function enables you to base conditional actions on the transaction state. An explicit transaction is any transaction that the BEGIN WORK statement starts. An implicit transaction is any transaction that the database server initiates and the BEGIN WORK statement does not start.

Return values

MI_NO_XACT: No transaction is currently in effect.
MI_IMPLICIT_XACT: An implicit transaction is currently in effect.
MI_EXPLICIT_XACT: An explicit transaction is currently in effect.