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_client() functionThe mi_client() function dynamically determines whether a DataBlade® API module is running in the database server or as a client application.

The mi_client() function

The mi_client() function dynamically determines whether a DataBlade® API module is running in the database server or as a client application.

Syntax

mi_integer mi_client()


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

Usage

The mi_client() function tells a DataBlade API module which implementation of the DataBlade API it is using, as follows:

C UDRs use the server-side implementation of the DataBlade API.
Client LIBMI applications use the client-side implementation of the DataBlade API.

This function is useful in DataBlade API code that runs in both the server-side and client-side implementations of the DataBlade API.

Return values

0: The DataBlade API module is running as a C UDR.
1: The DataBlade API module is running as a client LIBMI application.
MI_ERROR: The function was not successful.

Rate this topic

5 stars 4 stars 3 stars 2 stars 1 star

Comment on this topic.

By clicking this box, you acknowledge that you are NOT a U.S. Federal Government employee or agency, nor are you submitting information with respect to or on behalf of one. HCL provides software and services to U.S. Federal Government customers through its partners immixGroup, Inc. Contact this team at https://hcltechsw.com/resources/us-government-contact. Do not include any personal data in this Comment box.