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.
Complete executionThe DataBlade® API provides functions to complete execution of the current statement.
Finish executionThe mi_query_finish() function completes execution of the current statement.
Process remaining rowsThe mi_exec() function opens an implicit cursor to hold the resulting rows of a query. For such queries, the mi_query_finish() function ensures that the database server processes the results of a statement. The mi_query_finish() function processes all the remaining rows in the cursor of the current statement and throws them away.

Process remaining rows

The mi_exec() function opens an implicit cursor to hold the resulting rows of a query. For such queries, the mi_query_finish() function ensures that the database server processes the results of a statement. The mi_query_finish() function processes all the remaining rows in the cursor of the current statement and throws them away.

If the current statement failed, mi_query_finish() returns MI_ERROR. In this case, mi_query_finish() guarantees that the database server is ready for the next statement (unless the database server has dropped the connection). All callbacks are properly invoked during mi_query_finish() processing.

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.