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 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 Informix® databases.
DataBlade® API Programmer's Guide
The 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
Exceptions and events
This section describes exceptions and events, and explains how to handle them in DataBlade® API modules.
State-transition events
When the database server raises a state-transition event, the database server invokes any callbacks registered for the state transition. This section provides information about state-transition handling in DataBlade® API modules, including an explanation of state-transition events and a description of how to handle a state-transition event in a C UDR and a client LIBMI application.
Providing state-transition handling
The database server throws a state-transition event when it changes its processing state.
State transitions in a C UDR (Server)

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.
- Informix® 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 Informix® databases.
  - DataBlade® API Programmer's Guide
    The Informix® DataBlade® API Programmer's Guide describes information about the DataBlade API, the C-language application programming interface (API) provided with HCL Informix.
    - DataBlade® API overview
    - Data manipulation
    - Database access
      - Connection handling
        This section describes how to initialize, establish, and close connections.
      - Execute SQL statements
        One basic task of a DataBlade® API module is to send SQL statements to the database server for execution.
      - Execute user-defined routines
        This section provides information about how to call a user-defined routine (UDR).
      - Exceptions and events
        This section describes exceptions and events, and explains how to handle them in DataBlade® API modules.
        DataBlade® API event types
        For a DataBlade® API module, an event is a communication from HCL Informix® software that indicates the existence of some predefined condition, usually the occurrence of an exception (warning or error). The DataBlade API represents an event as one of the enumerated values of the MI_EVENT_TYPE data type.
        Event-handling mechanisms
        An event-handling mechanism provides a way for one DataBlade® API module to inform another module (or another part of the same module) that an event has occurred during execution of a function.
        Callback functions
        To catch or handle an event, you create a C function called a callback function. In your DataBlade® API module, you can register callback functions to handle recovery from events. The DataBlade API invokes a registered (and enabled) callback when the event associated with the callback occurs.
        Database server exceptions
        When the database server or a UDR raises a database server exception, the DataBlade® API invokes any callbacks that are registered for the exception.
        State-transition events
        When the database server raises a state-transition event, the database server invokes any callbacks registered for the state transition. This section provides information about state-transition handling in DataBlade® API modules, including an explanation of state-transition events and a description of how to handle a state-transition event in a C UDR and a client LIBMI application.
        Understanding state-transition events
        State-transition events occur when the database server changes its processing state. The DataBlade® API represents a state transition as one of the enumerated values of the MI_TRANSITION_TYPE data type.
        Providing state-transition handling
        The database server throws a state-transition event when it changes its processing state.
        State transitions in a C UDR (Server)
        Manage memory allocations
        If your code allocates memory for user data that the callback function needs, this memory must have a duration long enough to persist until the execution of the callback. Otherwise, the callback cannot access the user data. This user data might include information that the callback function needs to handle the event or to notify users of the cause of the event.
        Manage the transaction
        The transaction system of the database server only guarantees transaction semantics on all objects that are internal to the database. However, transactions might also include operations on external objects. A UDR might perform such operations, such as creating a temporary file or sending a message.
        State transitions in a client LIBMI application
        In a client LIBMI application, the only state-transition event that might occur is MI_Xact_State_Change. The MI_Xact_State_Change event occurs only within a client application.
        Client LIBMI errors
        The DataBlade® API throws the MI_Client_Library_Error event to indicate an error in the client LIBMI library.
      - XA-compliant external data sources
    - Create user-defined routines
    - Appendix
      This section contains additional reference information.
  - DataBlade® API Function Reference
    The Informix® DataBlade® API Function Reference describes the DataBlade API functions and the subset of Informix ESQL/C 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 Informix® databases.
  - J/Foundation Developer's Guide
    The J/Foundation Developer's Guide describes how to write user-defined routines (UDRs) in the Java™ programming language for Informix®.
  - R-Tree Index User's Guide
    The Informix® R-Tree Index User's Guide describes the HCL Informix R-tree secondary access method and how to access and use its components.
  - User-Defined Routines and Data Types Developer's Guide
    The Informix® 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 Informix.
  - Virtual-Table Interface Guide
    The 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.
  - Virtual-Index Interface Guide
    The Informix® Virtual-Index Interface Programmer's Guide explains how to create a secondary access method with the Virtual-Index Interface (VII) to extend the built-in indexing schemes of HCL Informix typically with a DataBlade® module.

State transitions in a C UDR (Server)

In a C UDR, the following state-transition events might occur:

MI_EVENT_SAVEPOINT
MI_EVENT_COMMIT_ABORT
MI_EVENT_POST_XACT
MI_EVENT_END_STMT
MI_EVENT_END_XACT
MI_EVENT_END_SESSION

For these state-transition events, the mi_transition_type() function returns a state-transaction type of normal end (MI_NORMAL_END) or abort end (MI_ABORT_END). In a UDR, state-transition callbacks are always called at the end of a transaction (normal or canceled), never at the beginning.