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™.
Develop a user-defined routine
Plan the routine

Plan the routine

When you write a UDR, consider the following:

Naming your routine
Defining routine parameters
Defining a return value (user-defined functions only)
Adhering to coding standards

The routine name and routine parameters make up the routine signature for the routine. The routine signature uniquely identifies the UDR in the database. For more information, see The routine signature.

Consider the following questions about routine naming and design:

Are any of my routines modal? That is, does the behavior of the routine depend on one of its arguments?
Can I describe what each type and routine does in two sentences?
Do any of my routines take more than three arguments?
Have I used polymorphism effectively?

If you plan to enable the implicit or explicit execution of a UDR across databases, all user-defined data types and casts must be defined in all of the participating databases of the same database server instance.