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 ActiveX value objectsThis section describes how to use the OneDB® DataBlade® Developers Kit (DBDK) to create ActiveX value objects. This section describes the use of C++ to implement opaque type support routines.
Implement ActiveX value objectsTo implement the client and server projects of an ActiveX value object, you add project-specific logic to particular C++ source files generated by BladeSmith.
Add project-specific logic to the source code

Add project-specific logic to the source code

For each routine in each support routine category that you specify for a particular opaque type, BladeSmith generates one of the following functions:

The function definition and a function body that contains only a call to DkErrorRaise(). These routines are indicated by the comment Developer: TO DO.
You must supply project-specific internal logic to these routines.
BladeSmith inserts the DkErrorRaise() method into these routines, naming the routine that has not been implemented and the file in which it is in. When you supply the logic to these routines, you can remove the call to DkErrorRaise() or modify it to return an error more appropriate to the added logic.
The function definition and a default function body. These routines are indicated by the comment Developer: Make changes in this section if necessary.
You can keep the default logic, or you can replace or modify it as appropriate for your project.