Home
Extending Informix®Beyond standard relational database objects, HCL Informix® can be extended to handle specialized data types, access methods, routines, and other objects. Informix® includes many built-in extensions that are fully integrated in the database server. Informix® 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 Informix®.
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 Informix® databases.
DataBlade® Developers KitThe 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 Informix® databases.
DataBlade® Developers Kit User's GuideThe HCL Informix® DataBlade® Developers Kit User's Guide describes how to use tools to develop and package DataBlade® modules.
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 Informix® on Windows™.
Debugging a DataBlade® moduleDebugging a DataBlade® module is usually an iterative process, repeated many times until the code is debugged.
Edit unit test filesBefore you start debugging, edit the unit test files to add the SQL statements necessary to debug your DataBlade® module.

Edit unit test files

Before you start debugging, edit the unit test files to add the SQL statements necessary to debug your DataBlade® module.

When you generate unit tests for a DataBlade module, BladeSmith generates the files listed in the following table in the src\tests directory.

Table 1. BladeSmith generated files
Test file	Purpose
Setup.sql	Optionally initializes the database. You can add SQL statements to create and populate the tables necessary for your debugging tests. If you specify this file as your initialization file in the Configure DBDK Visual C++ Add-In dialog box, IfxQuery automatically runs this file after it creates a database.
`Routine`.sql	Tests the user-defined routine. You can add SQL statements or modify the sample data for the routine. Use this file if you are debugging udr.c. IfxQuery runs this file if you click Debug DataBlade Module with this file in the active window.
`Opaque`.sql	Tests the support routines for each opaque data type. You can add SQL statements or modify the sample data for each support routine. Use this file if you are debugging Opaque.c or OpaqueServer.cpp. IfxQuery runs this file if you click Debug DataBlade Module with this file in the active window.
Cleanup.sql	Optionally deletes and drops tables and data in your test database. IfxQuery runs this file if you click Debug DataBlade Module with this file in the active window.

When you edit unit test files, add SQL statements in the areas marked with TEST comments. This ensures that your statements are merged when you regenerate unit tests with BladeSmith.

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.