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.
J/Foundation Developer's GuideThe HCL® J/Foundation Developer's Guide describes how to write user-defined routines (UDRs) in the Java™ programming language for HCL OneDB™.
Opaque user-defined data typesThis section describes how to use opaque user-defined data types (UDTs). This section describes the default SQLData interface and how to override the default.
Override the default I/O methodsIf the default methods are not sufficient because, for example, you want to include parentheses and other delimiting characters in the text representation, you can explicitly override the defaults with definitions of your own, after you register the Java™ UDT.
I/O function sets and related types
IfxDataPointerThe IfxDataPointer class encapsulates the HCL OneDB™ C-language representation of a type and its corresponding data buffer. This is usually a database server buffer structure, with a few attributes extracted for easy access in Java™ code.

IfxDataPointer

The IfxDataPointer class encapsulates the HCL OneDB™ C-language representation of a type and its corresponding data buffer. This is usually a database server buffer structure, with a few attributes extracted for easy access in Java™ code.

This class is used to transport the nontextual SQL data types to and from the I/O methods and is generally managed by an IfmxUDTSQLInput or IfmxUDTSQLOutput stream.

Methods in both streams might throw an SQLException with the e.getErrorcode equal to -79700 or IfxErrMsg.S_MTHNSUPP, if they are not implemented. These methods are generally not needed on the database server side but are useful in the client OneDB JDBC Driver code.

For more documentation of these streams, see the HCL OneDB JDBC Driver Programmer's Guide. For an example of using these streams, see Usage example.