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.
User-Defined Routines and Data Types Developer's GuideThe HCL OneDB™ User-Defined Routines and Data Types Developer's Guide describes how to define new data types and enable user-defined routines (UDRs) to extend HCL OneDB™.
Create an opaque data type
Creating an opaque data type
Creating UDT-to-Java mappings

Creating UDT-to-Java mappings

About this task

The routine manager needs a mapping between SQL data values and Java™ objects to be able to pass parameters to and retrieve return results from a UDR. The SQL to Java data-type mapping is performed according to the JDBC specification. For built-in SQL data types, the routine manager can use mappings to existing JDBC data types.

To create the mapping between a user-defined SQL data type and a Java object:

Procedure

Create a user-defined class that implements the SQLData interface. (For more information, refer to the JDBC 2.0 specification).
Bind this user-defined class to the user-defined SQL data type using the setUDTExtName built-in procedure.