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.
Create DataBlade® module objectsBladeSmith uses wizards to create and edit objects.
Create data typesYou can create extended data types in BladeSmith. In addition, you must define qualified built-in data types before you can use them in a BladeSmith project.
Row data typeA row data type is a group of fields of existing data types arranged like a row in a table. The fields of a row data type can be almost any data type that exists in your project, including other row data types.

Row data type

A row data type is a group of fields of existing data types arranged like a row in a table. The fields of a row data type can be almost any data type that exists in your project, including other row data types.

You can overload existing user-defined routines and built-in routines to work on your row type.

The following table lists the properties you specify when you create a row data type.

Table 1. Properties for creating a row data type
Property	Default value	Description
Name	prefixRowType	The name of the row type. Must be unique. To create an unnamed row type, leave this field blank. See Named and Unnamed Row data types for more information.
Inherits from parent?	No parent	A row type can inherit the fields and routines of another (parent) row type. See Named and Unnamed Row data types for more information.
Field information	None	The name, data type, and nullability of the fields within the row type. See Row data type fields for more information.