Jump to main content
Product Documentation
Customer Support
HCL OneDB 2.0.1
What's new in
HCL OneDB™
2.0.1
Getting Started
Installing
Administering
Migrating and upgrading
Data warehousing
Security
Client APIs and tools
SQL programming
JSON compatibility
Extending
HCL OneDB™
Designing databases
Embedding
HCL OneDB™
Release information
Troubleshooting
HCL OneDB™
Search
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 extensions
You 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.
DataBlade®
Developers Kit
The
DataBlade®
Developers Kit (DBDK) guides contain information about the tools you can use to develop and package
DataBlade®
modules, which extend the functionality of
HCL OneDB™
databases.
DataBlade®
Developers Kit User's Guide
The
HCL OneDB™
DataBlade®
Developers Kit Users Guide
describes how to use
DataBlade® Developers Kit (DBDK)
tools to develop and package
DataBlade®
modules.
Design
DataBlade®
modules
This section describes the
DataBlade®
module SQL design issues.
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™
.
HCL OneDB™
extensions and
DataBlade®
modules
These topics describe how to use built-in database extensions and separately installed
DataBlade®
modules.
Creating extensions
You 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.
DataBlade® API
Function Reference
The
HCL OneDB™ DataBlade® API Function Reference
describes the
DataBlade® API
functions and the subset of functions that the
DataBlade® API
supports.
DataBlade®
Developers Kit
The
DataBlade®
Developers Kit (DBDK) guides contain information about the tools you can use to develop and package
DataBlade®
modules, which extend the functionality of
HCL OneDB™
databases.
DataBlade Module Development Overview
DataBlade®
Developers Kit User's Guide
The
HCL OneDB™
DataBlade®
Developers Kit Users Guide
describes how to use
DataBlade® Developers Kit (DBDK)
tools to develop and package
DataBlade®
modules.
Getting started with
DataBlade®
module development
This section provides an overview of
DataBlade®
module development and describes the resources and tools the
HCL OneDB™
database server provides to facilitate development.
Design
DataBlade®
modules
This section describes the
DataBlade®
module SQL design issues.
Data model
A data model is a high-level definition of a
DataBlade®
module: what objects it represents and what operations on those objects it provides.
Data type design
After you have designed a data model for your
DataBlade®
module, you can design its specifics, such as data types to best represent your
DataBlade®
module objects.
Query language interface
The next component in
DataBlade®
module design is the query language interface.
Query processing
To develop a
DataBlade®
module, you need a general understanding of query processing and
HCL OneDB™
SQL. You must also understand the execution environment inside your
HCL OneDB™
database server ̵ the multithreading model, the collection of processes in which
DataBlade®
module routines can execute, and concurrent access to database objects, transactions, and so on.
Interoperability
The interoperability of a
DataBlade®
module refers to how well that module works with your
HCL OneDB™
database server and with other
DataBlade®
modules.
Programming guidelines
Use this section to help you when you write the design specification for your
DataBlade®
module.
Create
DataBlade®
objects by using BladeSmith
Use BladeSmith to create
DataBlade®
modules.
Programming
DataBlade®
module routines in C
This section contains information to help you edit and compile C language source code generated by
DataBlade®
.
Create ActiveX value objects
This section describes how to use the
DataBlade® Developers Kit (DBDK)
to create ActiveX value objects. This section describes the use of C++ to implement opaque type support routines.
The ActiveX value objects
This section provides information for client application developers who are using ActiveX value objects.
Programming
DataBlade®
modules in Java™
This section contains information to help you edit and compile Java™ language source code generated by BladeSmith.
Debugging and testing
DataBlade®
modules on UNIX™
This section describes how to debug and perform functional tests for
DataBlade®
modules written in C for
HCL OneDB™
on UNIX™.
Debugging and testing
DataBlade®
modules on Windows™
This section describes how to debug and perform functional tests for
DataBlade®
modules written in C and C++ for
HCL OneDB™
on Windows™.
BladePack
BladePack creates installation packages for
DataBlade®
modules and other software products.
Appendixes
This section contains additional reference information.
DBDK InfoShelf
The
DataBlade®
Developers Kit InfoShelf is designed to help you work with BladeSmith.
J/Foundation Developer's Guide
The
HCL® J/Foundation Developer's Guide
describes how to write user-defined routines (UDRs) in the Java™ programming language for
HCL OneDB™
.
User-Defined Routines and Data Types Developer's Guide
The
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™
.
Design
DataBlade
modules
This section describes the
DataBlade®
module SQL design issues.
Data model
A data model is a high-level definition of a
DataBlade
module: what objects it represents and what operations on those objects it provides.
Data type design
After you have designed a data model for your
DataBlade
module, you can design its specifics, such as data types to best represent your
DataBlade
module objects.
Query language interface
The next component in
DataBlade
module design is the query language interface.
Query processing
To develop a
DataBlade
module, you need a general understanding of query processing and
HCL OneDB™
SQL. You must also understand the execution environment inside your
HCL OneDB™
database server ̵ the multithreading model, the collection of processes in which
DataBlade
module routines can execute, and concurrent access to database objects, transactions, and so on.
Interoperability
The interoperability of a
DataBlade
module refers to how well that module works with your
HCL OneDB™
database server and with other
DataBlade
modules.
Rate this topic
5 stars
4 stars
3 stars
2 stars
1 star
Comment on this topic.
By clicking this box, you acknowledge that you are NOT a U.S. Federal Government employee or agency, nor are you submitting information with respect to or on behalf of one. HCL provides software and services to U.S. Federal Government customers through its partners immixGroup, Inc. Contact this team at
https://hcltechsw.com/resources/us-government-contact
. Do not include any personal data in this Comment box.