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.
AppendixesThis section contains additional reference information.
Source files generated for DataBlade® modulesYou can use the tables in this section to find a brief description of the types of files BladeSmith generates for your DataBlade® project.
SQL script files

SQL script files

BladeSmith generates the following SQL scripts in the project\scripts directory.

Table 1. SQL script files
File name	Description
errors.locale	Contains locale-specific error messages. For example, the file for the default US English locale is errors.en_us.1252. This file is only generated if you define new error messages for your DataBlade® module.
objects.sql	Contains SQL statements that update the sysbldobjects system table with information about the DataBlade module objects that are created in a database. BladeManager uses the information in the table to register, unregister, and upgrade DataBlade modules.
prepare.locale.sql	Contains SQL statements for locale-specific objects. For example, the file for the default US English locale is prepare.en_us.sql.
prepare.sql	Contains SQL statements that describe the DataBlade module to BladeManager.