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_specset_extsz() functionThe mi_lo_specset_extsz() function sets the allocation extent size for a smart large object.

The mi_lo_specset_extsz() function

The mi_lo_specset_extsz() function sets the allocation extent size for a smart large object.

Syntax

mi_integer mi_lo_specget_extsz(LO_spec, extsz)
   MI_LO_SPEC *LO_spec;
   mi_integer extsz;

LO_spec: A pointer to the LO-specification structure in which to save the extend size.
extsz: An integer value for the size, in kilobytes, of the allocation extent of a smart large object.


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

Usage

The mi_lo_specset_extsz() function is the LO-specification accessor function that sets the allocation extent size for a new smart large object. The extsz value specifies the size of the allocation extents to be allocated for the smart large object when the smart-large-object optimizer writes beyond the end of the current extent.

Important: Before you call mi_lo_specset_extsz(), you must initialize an LO-specification structure.

When you set the extent size with mi_lo_specset_extsz(), you override any column-level or system-specified extent size in the LO-specification structure. You then pass this LO-specification structure to a smart-large-object creation function (such as mi_lo_create()) to provide the extent size as a user-supplied storage characteristic for a new smart large object.

The smart-large-object optimizer attempts to optimize the extent size based on past operations on the smart large object and other storage characteristics (such as maximum bytes) that it obtains from the storage-characteristics hierarchy. Most applications can use this generated extent size.

Important: Do not change the system-specified extent size unless your application encounters severe storage fragmentation. For such applications, make sure that you know exactly the number of bytes by which to extend the smart large object.

For more information about the allocation extent size of a smart large object or on how to use the mi_lo_specset_extsz() function, see the HCL OneDB™ DataBlade® API Programmer's Guide.

Return values

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