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 a project
New object prefixUse a three-character object prefix in the name of the new objects you create in BladeSmith to ensure that your objects have unique names in the database when the DataBlade® module is registered.

New object prefix

Use a three-character object prefix in the name of the new objects you create in BladeSmith to ensure that your objects have unique names in the database when the DataBlade® module is registered.

Use your DataBlade module new object prefix to begin the names of the following objects:

New data types
User-defined routines
Aggregates
Access methods
Executable utilities and tools provided with the DataBlade module
Tables, views, and other custom SQL objects included with your DataBlade module
User-defined virtual processors
Trace classes
Named memory

You do not have to use the DataBlade module new object prefix for the following objects:

Names of routines that operate on data types unique to your DataBlade module, including routines that you overload to take a new data type
Names of routines that operate on data types provided by other DataBlade modules that you develop and maintain
Names of routines in support libraries linked to the shared object file

Have feedback?
Google Analytics is used to store comments and ratings. To provide a comment or rating for a topic, click Accept All Cookies or Allow All in Cookie Preferences in the footer of this page.