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® Developers KitThe DataBlade® Developers Kit (DBDK) guides contain information about the tools you can use to develop and package DataBlade® modules, which extend the functionality of HCL OneDB™ databases.
DataBlade® Developers Kit User's GuideThe HCL OneDB™ DataBlade® Developers Kit Users Guide describes how to use OneDB® DataBlade® Developers Kit (DBDK) tools to develop and package DataBlade® modules.
Create DataBlade® objects by using BladeSmithUse BladeSmith to create DataBlade® modules.
Perform functional test dataYou can perform functional tests on your DataBlade® module routines by using the functional tests generated by BladeSmith. You must enter test data for functional tests in BladeSmith. You run functional tests on UNIX™, or you run them on Windows™ by using a toolkit that is compatible with UNIX™, such as MKS Toolkit.
Test data for cast support routinesTo enter test data for a cast support function, select the cast and choose Edit > Gather Test Data.

Test data for cast support routines

To enter test data for a cast support function, select the cast and choose Edit > Gather Test Data.

The test data for a cast support function includes the following items:

Input data, in the text input format specified for the source data type.
Expected output data, in the text output format specified for the destination data type.
The error code expected if the input data is not valid. If the input data is valid, leave this field blank.

Enter invalid input values and values that test boundary conditions for the data type.