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-Index Interface GuideThe 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.
Develop an access methodThese topics describe the steps that you take to implement a user-defined access method with the Virtual-Index Interface (VII).
Testing the access methodTo test the access method, take the same actions that users of the access method take to create and access virtual data.
Create and specify storage spacesA storage space is a physical area where the table data is stored. To test how the access method builds new indexes, you create a new physical storage space before you create the index.
Avoid storage-space errors

Avoid storage-space errors

An SQL error occurs if you include an IN clause with the CREATE INDEX statement and one of the following conditions is true:

The IN clause specifies an extspace or sbspace that does not exist.
The IN clause specifies an sbspace, but the am_sptype purpose value is set to X.
The IN clause specifies an extspace, but the am_sptype purpose value is set to S.

An SQL error occurs if the CREATE INDEX statement contains no IN clause and one of the following conditions is true:

The am_sptype purpose value is set to A, no default SBSPACENAME exists, and the access method does not create an extspace.
The am_sptype purpose value is set to S, and no default SBSPACENAME exists.
The am_sptype purpose value is set to X, and the access method does not create an extspace.

An SQL error occurs if one of the following conditions is true:

The am_sptype purpose value is set to D.
The IN clause with the CREATE INDEX statement specifies a dbspace, even if the am_sptype purpose value is set to A.

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.