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_interval_compare() functionThe mi_interval_compare() function compares two binary (internal) INTERVAL values and returns an integer value that indicates whether the first value is before, equal to, or after the second value.

The mi_interval_compare() function

The mi_interval_compare() function compares two binary (internal) INTERVAL values and returns an integer value that indicates whether the first value is before, equal to, or after the second value.

Syntax

mi_integer
mi_interval_compare(mi_interval *inv1, mi_interval *inv2, 
                    mi_integer *result)

inv1: is a pointer to an internal INTERVAL representation of the interval value.
inv2: is a pointer to an internal INTERVAL representation of the interval value.
result: is a pointer to the result of the comparison.


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

Usage

Use the mi_interval_compare() function to compare the two interval values. If successful, the function returns MI_OK and sets the result variable to one of the following values:

-2: indicates that one or both of the INTERVAL values passed are NULL and cannot be compared.
-1: indicates that the value of inv1 is before the value of inv2.
0: indicates that the value of inv1 is equal to the value of inv2.
1: indicates that the value of inv1 is after the value of inv2.

Return values

MI_OK: indicates that the function was successful and that the value of the result variable was set.
-7520: indicates that one of the arguments passed is a NULL pointer.
-1263: indicates that a field in an INTERVAL data type is out of range, incorrect, or missing.
-1266: indicates that the INTERVAL values are incompatible for the operation.
-1268: indicates that there is an invalid INTERVAL qualifier.