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.
Programming DataBlade® module routines in CThis section contains information to help you edit and compile C language source code generated by DataBlade®.
Generated code
Tracing and error handlingBladeSmith adds tracing and error handling code throughout the generated source code if the tracing option is set to True when you generate source code in BladeSmith.
Enabling tracing in a DataBlade® moduleAfter you generate code with tracing and compile your code, enable tracing in your DataBlade® module.
Create the TraceSet_project() procedureThe TraceSet_project() procedure (where project is the name of your DataBlade® module project) sets the tracing output file and the trace threshold for a database server session by calling the DataBlade® API functions mi_tracefile_set() and mi_tracelevel_set().
Syntax for the TraceSet_project() procedure

Syntax for the TraceSet_project() procedure

The syntax for using the TraceSet_project() procedure is as follows:

EXECUTE PROCEDURE TraceSet_project(
          "traceFile",
          traceThreshold
);

traceFile

The path and file name of the trace output file for the current database server session, surrounded by quotation marks. If you do not specify a file name, the default file, /tmp/session_ID.trc, is created. If you specify a file name and then execute TraceSet_project() again during the same session without specifying a file name, the file name is not changed.

traceThreshold

The trace threshold for the current database server session. There are three possible values:

0: Tracing is disabled.
> 0: Tracing is enabled and the threshold is set to that number.
< 0: The tracing threshold is not changed.