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™.
Improve UDR performance
Parallel UDRs
Enable parallel UDRs
Write PDQ threadsafe UDRs

Write PDQ threadsafe UDRs

External-language UDRs can execute in parallel as long as they are PDQ threadsafe DataBlade® API functions.

The following DataBlade API function categories are PDQ thread safe:

Data handling
Exception in this category: collection manipulation functions (mi_collection_*) are not PDQ thread safe.
Session, thread, and transaction management
Function execution
Memory management
Exception handling
Callbacks
Miscellaneous

If an external-language UDR calls a non-PDQ threadsafe function that was created with the PARALLELIZABLE modifier, the database server aborts the query and issues the following error message:

-7422 Can not issue DAPI function %s in a secondary 
PDQ thread.

The database server substitutes the name of the DataBlade API function for the %s string in this error message.