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_fix_integer() functionThe mi_fix_integer() function converts the specified 4-byte integer to or from the byte order of the client computer.

The mi_fix_integer() function

The mi_fix_integer() function converts the specified 4-byte integer to or from the byte order of the client computer.

Syntax

mi_unsigned_integer mi_fix_integer(val)
   mi_unsigned_integer val;

val: The 4-byte integer value on which to fix the byte order.


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

Usage

The mi_fix_integer() function is useful in send and receive support functions for an opaque data type when the opaque-type structure contains an mi_integer component that needs to be converted to and from the client byte order.

Return values

An mi_unsigned_integer value: The value in the desired byte order.
MI_ERROR: The function was not successful.