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_lo_stat_ctime() functionThe mi_lo_stat_ctime() function returns from an LO-status structure the last-change time for a smart large object.

The mi_lo_stat_ctime() function

The mi_lo_stat_ctime() function returns from an LO-status structure the last-change time for a smart large object.

Syntax

mi_integer mi_lo_stat_ctime(LO_stat)
   MI_LO_STAT *LO_stat;

LO_stat: A pointer to an LO-status structure that mi_lo_stat() allocates and fills in with status information.


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

Usage

The mi_lo_stat_ctime() function obtains the last-change time from the LO-status structure that LO_stat references. The last-change time includes changes to metadata (modification of storage characteristics, a change in the number of references) and user data (writes to the smart large object). The resolution of the last-change time that the mi_lo_stat_ctime() function returns is number of seconds since 00:00:00, January 1, 1970.

Important: Before you call mi_lo_stat_ctime(), you must initialize an LO-status structure with the mi_lo_stat() function.

For more information about the last-change time of a smart large object or about how to use an LO-status structure, see the HCL OneDB™ DataBlade® API Programmer's Guide.

Return values

>=0: The number of seconds since January 1, 1970 for the last-change time of the smart large object whose status information is in the LO-status structure that LO_stat references.
MI_ERROR: The function was not successful.