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_mtime_usec() functionThe mi_lo_stat_mtime_usec() function returns from an LO-status structure the microsecond component of the last-modification time for a smart large object.

The mi_lo_stat_mtime_usec() function

The mi_lo_stat_mtime_usec() function returns from an LO-status structure the microsecond component of the last-modification time for a smart large object.

Syntax

mi_integer mi_lo_stat_mtime_usec(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_mtime_usec() function obtains the microsecond component of the last-modification time from the LO-status structure that LO_stat references. The last-modification time includes changes to user data (writes to the smart large object) only.

Important: The database server does not maintain the microsecond component of last-modification time. If your platform supports the microsecond component of system time and you choose to maintain it for smart large objects, you must explicitly set the last-modification microsecond value with the mi_lo_utimes() function.

If the microsecond component of last-modification time is supported and maintained on your system, the mi_lo_stat_mtime_usec() function can obtain it from an initialized LO-status structure. To return the seconds component of the time of last modification, use the mi_lo_stat_mtime_usec() function. The database server does maintain this seconds component of the last-modification time.

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

For more information about the last-modification 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 microseconds in the last-modification time for the smart large object that LO_stat references.
MI_ERROR: 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.