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_date_to_binary() functionThe mi_date_to_binary() function converts a text (string) representation of a date value to its binary (internal) DATE representation.

The mi_date_to_binary() function

The mi_date_to_binary() function converts a text (string) representation of a date value to its binary (internal) DATE representation.

Syntax

mi_date mi_date_to_binary(date_string)
   mi_lvarchar *date_string;

date_string: A pointer to the date string to convert to its internal DATE format.


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

Usage

The mi_date_to_binary() function converts the date string that date_string references to the internal DATE value. An internal DATE value is the format that the database server uses to store a date in a column of the database.

For GLS, the mi_date_to_binary() function accepts the date string in the date format of the current processing locale. The function also performs any code-set conversion necessary between the current processing locale and the target locale.

Important: The mi_date_to_binary() function is supported only for compatibility with earlier versions of existing DataBlade® API modules. The DataBlade API will eventually discontinue support for this function. Use the mi_string_to_date() function in any new DataBlade API modules.

Return values

An mi_date value: The internal (binary) DATE representation of date_string.
NULL: The function was not successful.