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.
Debugging and testing DataBlade® modules on UNIX™This section describes how to debug and perform functional tests for DataBlade® modules written in C for HCL OneDB™ on UNIX™.
Debugging a DataBlade® moduleDebugging a DataBlade® module is usually an iterative process, repeated many times until the code is debugged.
Set breakpointsYou can set breakpoints in any routine with an entry point known to dbx.

Set breakpoints

You can set breakpoints in any routine with an entry point known to dbx.

HCL OneDB™ database server software is compiled with debugging support turned off, so local storage and line number information is not available for database server routines. However, after you compile the DataBlade® module for debugging, you can see line number information and local storage for your functions.

When you enter a command in the client that calls one of your DataBlade module routines, the debugger stops in the routine. Then you can follow the steps of your routine. Because your DataBlade module is compiled with debugging support, you can view the local variables and stack for your routines.