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_tell() functionThe mi_lo_tell() function returns the current LO seek position for an open smart large object, relative to the beginning of the smart large object.

The mi_lo_tell() function

The mi_lo_tell() function returns the current LO seek position for an open smart large object, relative to the beginning of the smart large object.

Syntax

mi_integer mi_lo_tell(conn, LO_fd, seek_pos)
   MI_CONNECTION *conn;
   MI_LO_FD LO_fd;
   mi_int8 *seek_pos;

conn

This value is one of the following connection values:

A pointer to a connection descriptor established by a previous call to mi_open(), mi_server_connect(), or mi_server_reconnect().

A NULL-valued pointer (database server only)

LO_fd

An LO file descriptor for the open smart large object whose LO seek position you want to determine.

seek_pos

A pointer to the eight-byte integer (mi_int8) into which mi_lo_tell() copies the current LO seek position.


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

Usage

The mi_lo_tell() function obtains the LO seek position for the smart large object that LO_fd references. The LO seek position is the offset for the next read or write operation on the smart large object that is associated with the LO file descriptor, LO_fd. The mi_lo_tell() function returns this seek position in the mi_int8 seek_pos variable. For more information about how to access eight-bit (INT8) integers, see the HCL OneDB™ DataBlade® API Programmer's Guide.

Server only: The mi_lo_tell() function does not need a connection descriptor to execute. If your UDR does not need a valid connection for other operations, you can specify a NULL-valued pointer for the conn parameter to establish a NULL connection. For information about the advantages of a NULL connection, see the HCL OneDB DataBlade API Programmer's Guide.

Return values

MI_OK: The function was successful.
MI_ERROR: The function was not successful.