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® API Programmer's GuideThe Informix® DataBlade® API Programmer's Guide describes information about the DataBlade® API, the C-language application programming interface (API) provided with HCL Informix®.
Database access
Execute SQL statementsOne basic task of a DataBlade® API module is to send SQL statements to the database server for execution.
Execute SQL statementsTo execute an SQL statement, a DataBlade® API module must send the SQL statement to the database server, where the statement is executed.
Execute prepared SQL statementsA prepared statement is an SQL statement that is parsed and ready for execution. For these statements, you prepare the statement once and execute it as many times as needed.
Release prepared-statement resourcesWhen your DataBlade® API module no longer needs a prepared statement, you can release the resources that it uses with the mi_close_statement() function (explicit cursor) or the mi_drop_prepared_statement() function (statement descriptor, including any cursor).
Drop a prepared statement

Drop a prepared statement

A statement descriptor describes a prepared statement. However, this DataBlade® API structure is not allocated from the memory-duration pools. Instead, its scope is from the time it is created with mi_prepare() until whichever of the following events occurs first:

The mi_drop_prepared_statement() function frees the statement descriptor.
The mi_close() function closes the connection.
The SQL statement that invoked the C UDR ends. (Server only)

To conserve resources, use the mi_drop_prepared_statement() function to explicitly deallocate the statement descriptor once your DataBlade API module no longer needs it. The mi_drop_prepared_statement() function is the destructor function for a statement descriptor. It frees the statement descriptor and any resources (such as an implicit or explicit cursor) that are associated with the statement descriptor. These resources include the prepared statement and any associated row cursor. After you drop a prepared statement, you must re-prepare it before it can be executed again.

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.