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.
Virtual-Table Interface GuideThe Informix® Virtual-Table Interface Programmer's Guide explains how to create a primary access method with the Virtual-Table Interface (VTI) so that users have a single SQL interface to HCL Informix® tables and to data that does not conform to the storage scheme of HCL Informix®.
Purpose-function referenceThese topics describe the purpose functions that the access-method developer provides.
Purpose-function syntaxThe database server expects a particular prototype for each purpose function. As the access-method developer, you program the actions of a purpose function but must use the parameters and return values that the Virtual-Table Interface (VTI) prototypes specify.
The am_close purpose functionThe database server calls am_close when the processing of a single SQL statement (SELECT, UPDATE, INSERT, DELETE, MERGE) completes.

The am_close purpose function

The database server calls am_close when the processing of a single SQL statement (SELECT, UPDATE, INSERT, DELETE, MERGE) completes.

Syntax

mi_integer am_close(MI_AM_TABLE_DESC *tableDesc)

tableDesc: Points to the table descriptor.

Usage

The am_close function might:

Deallocate user-data memory that am_open allocated with a PER_STMT_EXEC or PER_STMT_PREP duration
Call mi_file_close(), mi_lo_close(), or one of the DataBlade® API functions that copies smart-large-object data to a file

Restriction: Do not call the DataBlade API mi_close() function to free a database connection handle that you open (in the am_open purpose function) with mi_open(). Because the database connection has a PER_COMMAND duration not a PER_STATEMENT duration, the database server frees the handle before it calls the am_close purpose function.

Return values

MI_OK: Indicates success.
MI_ERROR: Indicates failure.

Related topics

DataBlade API functions, such as mi_file_close() or mi_lo_close(), in the Informix® DataBlade API Programmer's Guide

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.