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
The routine signature
ANSI and non-ANSI routine signatures

ANSI and non-ANSI routine signatures

In a database that is not ANSI-compliant, the routine signature must be unique within the entire database, irrespective of the owner. If you explicitly qualify the routine name with an owner name, the signature includes the owner name as part of the routine name.

In an ANSI-compliant database, the routine signature must be unique within the name space of the user. The routine name always begins with the owner, in the following format:

owner.routine_name

When you register the routine signature in a database with the CREATE FUNCTION or CREATE PROCEDURE statement, the database server stores the routine signature in the sysprocedures system catalog table. For more information, see Registering a user-defined routine.