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_datetime_to_string() functionThe mi_datetime_to_string() function creates an ANSI SQL standard text (string) representation of a date, time, or date and time value from the binary (internal) DATETIME representation.

The mi_datetime_to_string() function

The mi_datetime_to_string() function creates an ANSI SQL standard text (string) representation of a date, time, or date and time value from the binary (internal) DATETIME representation.

Syntax

mi_string *mi_datetime_to_string(dt_data)
   mi_datetime *dt_data;

dt_data: A pointer to the internal DATETIME representation of the date, time, or date and time value.


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

Usage

The mi_datetime_to_string() function converts the internal DATETIME value that dt_data references into a date, time, or date and time string. This string has the following ANSI SQL standard format:

"YYYY-MM-DD HH:mm:SS.FFFFF"

YYYY: The 4-digit year.
MM: The 2-digit month.
DD: The 2-digit day.
HH: The 2-digit hour.
mm: The 2-digit minute.
SS: The 2-digit second.
FFFFF: The fraction of a second, in which the date, time, or date and time qualifier specifies the number of digits, with a maximum precision of 5 digits.

If the internal DATETIME value contains only a subset of this range, mi_datetime_to_string() creates a date, time, or date and time string with the appropriate portion of the preceding format. For example, suppose dt_data references the internal format of the date 01/31/07 and a time of 10:30 A.M. The mi_datetime_to_string() function returns an mi_string value with the following date and time string:

"2007-01-31 10:30"

Important: The mi_datetime_to_string() function replaces the mi_binary_to_datetime() function for conversion of a DATETIME value to a date, time, or date and time string in DataBlade® API modules.

For GLS, the mi_datetime_to_string() function does not format the date, time, or date and time string in the date and time formats of the current processing locale.

For more information about how to convert internal DATETIME values to date, time, or date and time strings, see the HCL OneDB™ DataBlade API Programmer's Guide.

Return values

An mi_string pointer: A pointer to the date, time, or date and time string equivalent of dt_data.
NULL: The function was not successful.

Have feedback?
Google Analytics is used to store comments and ratings. To provide a comment or rating for a topic, click Accept All Cookies or Allow All in Cookie Preferences in the footer of this page.