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_type_full_name() functionThe mi_type_full_name() function obtains the full name (owner.typename) of a data type from its type descriptor.

The mi_type_full_name() function

The mi_type_full_name() function obtains the full name (owner.typename) of a data type from its type descriptor.

Syntax

mi_string *mi_type_full_name(type_desc)
   MI_TYPE_DESC *type_desc;

type_desc: A pointer to the type descriptor from which to obtain the full name of the data type.


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

The mi_type_full_name() function determines the full name for the data type that type_desc references.

An mi_string pointer: A pointer to the full name of the data type in the type_desc type descriptor.
NULL: The function was not successful.