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™.
HCL OneDB™ extensions and DataBlade® modulesThese topics describe how to use built-in database extensions and separately installed DataBlade® modules.
Excalibur Text Search DataBlade® Module User's GuideThese topics describe the module and how to access and use its components.
AdministrationThe purpose of this section is to make database administrators aware of configuration and performance issues related to the features of the module.
Choose the appropriate storage data typeYou can improve performance by choosing the appropriate storage data type for your data. This section describes the advantages and disadvantages of storing text documents in the following supported data types: BLOB, CLOB, LVARCHAR, IfxDocDesc, and IfxMRData.
The LVARCHAR data typeText documents inserted into columns of type LVARCHAR are stored in dbspaces, like data inserted into the standard SQL character data types such as CHAR and VARCHAR. This incurs less resource overhead than storing documents in sbspaces, which is where data in BLOB and CLOB columns are stored.

The LVARCHAR data type

Text documents inserted into columns of type LVARCHAR are stored in dbspaces, like data inserted into the standard SQL character data types such as CHAR and VARCHAR. This incurs less resource overhead than storing documents in sbspaces, which is where data in BLOB and CLOB columns are stored.

The disadvantage of storing documents in columns of type LVARCHAR is that the size of the documents is limited to 32 KB.