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_version_comparison() functionThe mi_version_comparison() function compares the version of two instances of HCL OneDB™.

The mi_version_comparison() function

The mi_version_comparison() function compares the version of two instances of HCL OneDB™.

Syntax

mi_integer mi_version_comparison(s1, s2)
   mi_char1 *s1;
   mi_char *s2;

s1: The starting string address of the version number to compare.
s2: The ending string address of the version number to compare.


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

Usage

The mi_version_comparison() function compares the version for the major, minor, and interim version numbers of two database servers. For example, for HCL OneDB 11.50.UC6, the major version is 11, the minor version is 50, and the interim number is 6. If the interim number is omitted in one of the strings, then both strings will only be compared for only the major and minor release numbers.

Important: You must always use the mi_version_comparison() function instead of using a string comparison.

Return values

MI_ERROR (-1): indicates an error in the strings that are passed.
2: The value of s1 is greater than the value of s2.
0: The values of s1 and s2 are equal.
-2: The value of s1 is less than the value of s2.