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_yield() functionThe mi_yield() routine yields processing to other database server threads.

The mi_yield() function

The mi_yield() routine yields processing to other database server threads.

Syntax

void mi_yield()


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

Usage

The mi_yield() function causes the thread that is executing the C UDR to yield control of the virtual processor that is executing it. When the virtual processor is released, it can execute other threads.

Use the mi_yield() call periodically when the routine does CPU or I/O intensive work. The mi_yield() routine is useful in portions of code, such as tight loops, that would otherwise tie up the processor.

Return values

None.