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™.
Run a user-defined routine
Understanding routine resolution

Understanding routine resolution

You can assign the same name to different UDRs, as long as the routine signature is unique. It is the routine signature that uniquely identifies a UDR, not the routine name alone. A routine that has many versions is called an overloaded routine. When you invoke an overloaded routine, the database server must uniquely identify which routine to execute. This process of identifying the UDR to execute is called routine resolution.

This section provides the following information about routine resolution:

What is the routine signature?
What is an overloaded routine?
How to you create overloaded routines?
What is the routine-resolution process?

You need to understand the routine-resolution process to:

Obtain the data results that you expect from a UDR.
Avoid unintentional side effects if the wrong UDR executes.
Understand when you need to write an overloaded routine.