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_sync() functionThe mi_file_sync() function forces a write to disk of all pages in an operating-system file.

The mi_file_sync() function

The mi_file_sync() function forces a write to disk of all pages in an operating-system file.

Syntax

mi_integer mi_file_sync(fd)
   mi_integer fd;

fd: The file descriptor of the file to be written to disk. The file descriptor is obtained by a previous call to the mi_file_open() function.


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

The mi_file_sync() function writes to disk all pages of the operating-system file that the fd file descriptor identifies.

Server only: This function can force a write only for a file that resides on the server computer.

The mi_file_sync() interface routine has no effect on Windows™ clients.

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