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™.
Extend data types
Extend the data type system
Operator classes
Extend operator classes

Extend operator classes

The default operator class provides only for built-in data types. You might want to extend an operator class to support an extended data type for the following reasons:

To enable the default operator class to handle values of the extended data type in a generic B-tree
To provide a new sequence for the values of the extended data type to be stored in a generic B-tree
To extend an operator class of some other secondary-access method so that it handles the extended data type

To extend or implement an operator class, you must define strategy and support functions that handle each extended data type you want to index. For more information, see Extend an operator class.

You must register each new operator class in the database with the CREATE OPCLASS statement. For information about this statement, refer to the HCL OneDB™ Guide to SQL: Syntax.