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_file_tell8() functionThe mi_file_tell8() function returns the current file seek position, relative to the beginning of the file, for an operating-system file of length greater than 2 GB.

The mi_file_tell8() function

The mi_file_tell8() function returns the current file seek position, relative to the beginning of the file, for an operating-system file of length greater than 2 GB.

Syntax

mi_integer mi_file_tell8(fd, telpos8)
   mi_integer fd;
   mi_int8  *telpos8;

fd: The file descriptor of the file whose seek position is requested. The file descriptor is obtained by a previous call to mi_file_open() function.
telpos8: A pointer to the eight-byte integer (mi_int8) into which mi_file_tell8() copies the current file seek position.


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

Usage

The mi_file_tell8() function obtains the seek position for the operating-system file that fd identifies. The file seek position is the offset for the next read or write operation on the file that is associated with the file descriptor, fd.

Server only: In a C UDR, this function can obtain the seek position of a file that resides on either the server or client computer. You specify the location of the file when you open it with the mi_file_open() function.

Return values

MI_OK: The function was successful and provides the current position in the telpos8 variable.
MI_ERROR: The function was not successful.

The mi_file_tell8() function does not throw an MI_Exception event when it encounters a runtime error. Therefore, it does not cause callbacks to start.